Bug 137758 - Tight extensions not thread-safe
Summary: Tight extensions not thread-safe
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.1.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Extension-Tight-Integration 137759
  Show dependency tree / graph
 
Reported: 2020-10-26 08:52 UTC by Heiko Tietze
Modified: 2020-11-05 12:48 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Tietze 2020-10-26 08:52:47 UTC 
Taking Stephan's comment from Gerrit https://gerrit.libreoffice.org/c/core/+/98226: 

<https://curl.haxx.se/libcurl/c/curl_easy_init.html> explains that calling curl_easy_init (as is called from SearchAndParseThread::execute via curlGet) is delicate in a multi-threaded process:  It calls curl_global_init if necessary, and that is not thread-safe, and may call non-thread-safe code in underlying libraries---and my assumption is that it calls non-thread-safe code in nss that then somehow caused the above use-after-poison.

I suggest to make it experimental and suspend the unit test for now.
Comment 1 Heiko Tietze 2020-11-05 12:48:06 UTC 
Guess this can be solved with https://gerrit.libreoffice.org/c/core/+/105169