We are using soffice headless as document generation engine. Here is the command line we use to start the server : soffice --headless --nologo --nodefault --norestore --nocrashreport --nolockcheck --nofirststartwizard --accept="socket,host=localhost,port=8100;urp;StarOffice.ServiceManager" After a first document composition using UNO Java SDK on any ODT document (we make some fields replacement, some images replacement, a table modification and a PDF export and then we dispose the ODT document), the soffice.bin goes into a 100% CPU state. It continues to answer to UNO requests, but it keeps using 100% of a single core. We are using LibreOffice 5.0.1 RPM distribution on Amazon Linux x64 2015.03 We had the same behaviour if we use the engine OpenOffice 4.0.1 I don't know if the behaviour is the same on Linux x86. We are using Xvfb as display manager, since Amazon Linux doesn't provide any window manager integration. Thank you very much for your help.
I precise that if I use soffice on Windows with the same client SDK generation program, the CPU usage is ok.
You could try getting a cachegrind trace: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_cachegrind_trace Note that you need LibO built with --enable-symbols Here is a master build with --enable-dbgutil which is equal: http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@70-TDF-dbg/current/ Set to NEEDINFO. Change back to UNCONFIRMED after you have provided further testing information.
Thank you very much for your feed-back. I tried to execute the libreOffice distribution version located in http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@70-TDF-dbg/current/, but it does not start : The command I launched is : soffice --headless --nologo --nodefault --norestore --nocrashreport --nolockcheck --nofirststartwizard --accept=socket,host=localhost,port=8200;urp;StarOffice.ServiceManager Here is the output I got : bootstap: file:///opt/libreoffice5.2.0.0.alpha/LibreOfficeDev_5.2.0.0.alpha0_Linux_x86-64_archive/program/bootstraprc user installation: file:///opt/libreoffice5.2.0.0.alpha/LibreOfficeDev_5.2.0.0.alpha0_Linux_x86-64_archive/libreofficedev/4 Generate pipe md5 for 'file:///opt/libreoffice5.2.0.0.alpha/LibreOfficeDev_5.2.0.0.alpha0_Linux_x86-64_archive/libreofficedev/4' result: /tmp/OSL_PIPE_0_SingleOfficeIPC_a285f3efcbd7415011a6cfa85f5e48a5 Failed to connect to pipe: /tmp/OSL_PIPE_0_SingleOfficeIPC_a285f3efcbd7415011a6cfa85f5e48a5 Is there a problem with this build ? Regards.
Perhaps.. The only newer debug build currently is this 32-bit one: http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86@71-TDF-dbg/current/
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20161010
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20161108
still present in LibreOffice 5.2.4.2.1 20m0 debian jessie
The problem has been resolved by itself ... I was on Amazon Linux 2015.09, and I have updated to Amazon Linux version 2017.03, and the problem has gone! The soffice.bin process has now a normal CPU behavior! Best regards !
A precision. My exact Linux version is : Linux version 4.1.13-18.26.amzn1.x86_64 (mockbuild@gobi-build-64010) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) I confirm that using this version, I don't have this problem anymore.
Thanks! Closing.