I convert files to PDFs using libreoffice and I've run into a crash that I do not believe has yet been reported. When several clients connect to headless instance of libreoffice in parallel, it may cause a crash -- libreoffice segfaults. I tried this with libreoffice 4.0.4.2, 4.2.5.2, and 4.3.0.4.
Created attachment 104830 [details] Python script to connect to libreoffice and issue multiple requests
Created attachment 104831 [details] Run several instances of the same command in parallel and return statuses
To reproduce, start libreoffice: /opt/libreoffice4.3/program/soffice --norestore --headless \ --accept='socket,host=localhost,port=8100;urp;StarOffice.ServiceManager' Start ten clients in another window: bash parallel.sh 10 /opt/libreoffice4.3/program/python \ uno-client -n 100 some-file.txt /tmp/some-file.pdf It should take under a minute to crash, sometimes much less than that.
Let's put the min version indicated in your description.
Confirmed on Linux and OSX / LibreOffice 4.3.2.2 -> Platform: All -> NEW
Created attachment 108394 [details] Linux 4.3.2.2 backtrace
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
The issue is still present in 5.0.3 on Linux.
Stephan: I'd like to give it a try with a build of master sources (I use enable-dbg-util so thought I could retrieve useful info) but I don't know how to do this. Must I put something specific in autogen.input for example?
(In reply to Julien Nabet from comment #9) > but I don't know how to do this do what?
Stephan Bergmann committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=26cbb3d1049e789a1c2f56599dbfe0f379fc4b3d Related tdf#82775: Check for disposed-ness It will be available in 5.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Stephan Bergmann committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=e83f31724e0f2cd4242e0b398c48578da53cb5c1 tdf#82775: Don't prematurely dispose single-instance services It will be available in 5.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Stephan Bergmann committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=d01888302b03a79bf7ccde6cbe8434b427164a75 tdf#82775: Make NumberFormatCodeMapper MT safe It will be available in 5.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Stephan Bergmann from comment #10) > (In reply to Julien Nabet from comment #9) > > but I don't know how to do this > > do what? Sorry for my previous comment. I was talking about launching the test. Indeed, I've got this: Traceback (most recent call last): File "uno-client", line 13, in <module> import uno It seems I've got a pb to run Python script which uses "import uno" with a build of master sources. With LO Debian LO package, no pb since there's these: python3-uno - Python-UNO bridge uno-libs3 - LibreOffice UNO runtime environment -- public shared libraries uno-libs3-dbg - LibreOffice UNO runtime environment -- public shared library debug symbols unoconv - converter between LibreOffice document formats
(In reply to Julien Nabet from comment #14) > Traceback (most recent call last): > File "uno-client", line 13, in <module> > import uno As stated in comment 3, use the LO installation's python exectuable rather than the one given in the shebang of attachment 104830 [details].
See no further problems running the provided test case with the three commits * <http://cgit.freedesktop.org/libreoffice/core/commit/?id=e83f31724e0f2cd4242e0b398c48578da53cb5c1> "tdf#82775: Don't prematurely dispose single-instance services" * <http://cgit.freedesktop.org/libreoffice/core/commit/?id=d01888302b03a79bf7ccde6cbe8434b427164a75> "tdf#82775: Make NumberFormatCodeMapper MT safe" * <http://cgit.freedesktop.org/libreoffice/core/commit/?id=c83b55564dab042e3fc1889920cbb4db8fe40117> "Use OUString::replaceAll" in place.
(In reply to Stephan Bergmann from comment #16) > * > <http://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=e83f31724e0f2cd4242e0b398c48578da53cb5c1> "tdf#82775: Don't prematurely > dispose single-instance services" > * > <http://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=d01888302b03a79bf7ccde6cbe8434b427164a75> "tdf#82775: Make > NumberFormatCodeMapper MT safe" > * > <http://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=c83b55564dab042e3fc1889920cbb4db8fe40117> "Use OUString::replaceAll" requested backports of those three commits to libreoffice-5-1 with <https://gerrit.libreoffice.org/21129>, <https://gerrit.libreoffice.org/21130>, <https://gerrit.libreoffice.org/21131>
Stephan Bergmann committed a patch related to this issue. It has been pushed to "libreoffice-5-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=537c7dcfc1e2a1a8ebd9ef12f5671725c7d5e014&h=libreoffice-5-1 tdf#82775: Don't prematurely dispose single-instance services It will be available in 5.1.0.2. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Stephan Bergmann committed a patch related to this issue. It has been pushed to "libreoffice-5-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=d4ff96c740695401acbb4bb9e6a15a3c9c14fc53&h=libreoffice-5-1 tdf#82775: Make NumberFormatCodeMapper MT safe It will be available in 5.1.0.2. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.