https://bugs.freedesktop.org/show_bug.cgi?id=57930
Priority: medium
Bug ID: 57930
Assignee: libreoffice-bugs@lists.freedesktop.org
Summary: Intermittant freeze in splash screen when starting
with a file to open
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: jwoi...@just42.net
Hardware: x86 (IA32)
Status: UNCONFIRMED
Version: 3.6.2.2 release
Component: UI
Product: LibreOffice
A number of my Linux users are having Libreoffice freeze during the splash
screen on an intermittant basis (that is, the splash screen freezes up before
the progress bar has completed its move to the right, and no other Libreoffice
windows appear). It has been determined that this only happens if they are
starting Libreoffice with a file to open (eg: from the command line with
"swriter foobar.odt" or double-clicking on an ODT file in a file manager
environment). However, the fault does not occur every time this is done. It's
hard to estimate the frequency, but my first order guess would be perhaps one
in every 20 starts. If Libreoffice is started without a file to open (eg: from
the command line with "swriter" or via a desktop icon) the fault does not seem
to be triggered. Similarly, opening a file when any component of Libreoffice
is already running successfully also does not trigger the bug in our
experience.
Attempting to open other documents with Libreoffice when the fault condition is
present is unsuccessful; unsurprisingly they appear to be blocking until the
first instance has started correctly.
This problem has most recently been observed in the Libreoffice 3.6.2 release.
We have been observing it at least since 3.5.0.
The bug appears to be far easier to trigger if the file being opened resides on
an NFS volume.
Libreoffice quickstart is not running on the affected system.
I have tried various hacks to work around this but they all fail to prevent the
intermittant freeze. Firstly, in the soffice script SAL_ENABLE_FILE_LOCKING
was set to 0. We then tried with it undefined. The SAL_NO_XINITTHREADS line
in the soffice script was commented out but again the fault recurred. Finally,
oosplash was made into a symlink to soffice.bin. Curiously the splash screen
was still shown, and disappointingly the intermittant fault sill occured when
this was in place.
The system on which this fault has been observed the most is a stock 32-bit
Slackware 13.1 Linux distribution (2 GB RAM, Pentium D (dual core) at 3.4 GHz,
Intel 82945G/GZ integrated graphics, intel Xorg driver, 2.6.33.4 kernel, xfce4
desktop). However, it has also been seen on a PC running 32-bit Slackware
13.37 (1 GB RAM, Athlon XP CPU at 2 GB, Nvidia GeForce2 MX graphics, Nouveau
Xorg drivers, 3.6.3 kernel, fvwm2 window manager, libreoffice started only from
command line).
At the time of the freeze there are two processes running: oosplash and
soffice.bin. The attachments gdb_info-oosplash and gdb_info-soffice provide
thread information about both these processes as recorded during a freeze. I
have tested through strace, and will attach an trace from a working
(strace-ok.log) and frozen (strace-freeze.log) invocation so long as I don't
run into size limitations. All these attachments were recorded while using
Libreoffice 3.5.5.
Finally, this may or may not be related to bug 50686. The description offered
in that bug suggests that the problem in bug 50686 is a freeze or immediate
quit, with no "normal" behaviour being observed. We are not seeing any
spontaneous application exits and the issue we're seeing is intermittant, so I
expect 50686 is a different issue.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
