Bug 51028 - Browsing network directory could hang on MacOS X
Summary: Browsing network directory could hang on MacOS X
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: framework (show other bugs)
Version:
(earliest affected)
3.5.2 release
Hardware: x86 (IA32) macOS (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-13 03:40 UTC by Pierre-Alain Dorange
Modified: 2014-12-10 11:44 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
crash report from MacOS X, could indicate what process was running fool (290.13 KB, text/rtf)
2012-06-13 03:40 UTC, Pierre-Alain Dorange
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre-Alain Dorange 2012-06-13 03:40:13 UTC
Created attachment 62958 [details]
crash report from MacOS X, could indicate what process was running fool

Sometime (can't find a way to reproduce each time) when saving a document, when i select a network volume (in the left panel of the MacOS X File Browing GUI) the LibreOffice GUI stop responding (and do not display directory contain). 

Result : the application is "working" but nothing appears (it should display the contain of the network volume).

Fix : kill LibreOffice application

Context : 
   MacOS X (from 10.4x to 10.6.8)
   It never append with any other software (specific to LO/OO)

This bug exist since long time but is not often (i got it once a month and i use LibreOffice everyday). I got this bug with OpenOffice too since 3.x.

I can find a way to reproduce it, it append only sometimes and only when selection network volume.

Find attach a copy of the last crash i got : not a real crash i invoke myself the application "kill" but as the GUI was blocked it was the only way...
Comment 1 Michael Meeks 2012-06-13 06:31:11 UTC
Thanks for the nice trace. It -looks- like a crash to me that is hidden behind this lock-up:

...
          146 mach_msg_trap + 10 (in libSystem.B.dylib) [0x957bdafa]
            6 JVM_Lseek + 143243 (in libclient.dylib) [0x2d9e613b]
              6 JVM_EnableCompiler + 14233 (in libclient.dylib) [0x2da4d119]
                6 JVM_EnableCompiler + 14471 (in libclient.dylib) [0x2da4d207]
                  6 JVM_Halt + 669 (in libclient.dylib) [0x2da7fcad]
                    6 JVM_Halt + 726 (in libclient.dylib) [0x2da7fce6]
                      6 exit + 33 (in libSystem.B.dylib) [0x957dcb14]
                        3 __cxa_finalize + 208 (in libSystem.B.dylib) [0x957dcbff]
                          1 __tcf_0 + 90 (in libswlo.dylib) [0x275f1aca]
                            1 SwDLL::~SwDLL() + 84 (in libswlo.dylib) [0x275f16e4]
                              1 _FinitCore() + 2798 (in libswlo.dylib) [0x26fca9ce]
                                1 SwFmtMeta::~SwFmtMeta() + 30 (in libswlo.dylib) [0x272fdffe]
                          1 ??? (in configmgr.uno.dylib + 151302) [0x180a7f06]
                            1 ??? (in configmgr.uno.dylib + 173189) [0x180ad485]

Looks like Java calls 'exit' (urgh!) That then seems to cause some hideous badness around threading and cleanup of static classes that (most likely) wedges things.

Of course, I might be mis-reading the trace - not sure what's going on; calling 'exit' from Java sounds rather odd.

Can you report your Java version and/or experiment with upgrading that ? and/or can you run it from a console and see if you get any helpful debugging output on the console as/when it crashes ? :-)

Thanks !
Comment 2 Pierre-Alain Dorange 2012-06-13 06:41:13 UTC
regarding java : java -version gave
    java version "1.6.0_17"
    Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248)
    Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01-101, mixed mode)

I'm not de developper and my main langage is French, but i think that the 'exit' is perhaps cause by my own exit request as a user : i killed LibreOffice, that's what bring the crash report.
I killed if via the MacOS GUI interface to kill process. And was obliged to kill it because when this bug occurs i've found no other way to stop LibreOffice hanging.
The bug do not kill the application, the bug hang the GUI.
Comment 3 Michael Meeks 2012-06-14 01:47:26 UTC
ah - sure, but if something pathalogically bad happens - code can call 'exit' itself, and - unfortunately that triggers a load of cleanup - which can lock the application up [ making a crash look like a hang ]. I suspect this is one of those cases from the traces :-)

I imagine if you forced an exit we'd see a signal handler instead here (which can suffer the same problem sometimes FWIW).

did you manage to run from a terminal / console to see if there was some helpful Java debug output there when the error occurs ? :-)
Comment 4 retired 2014-12-10 11:43:19 UTC
Does this persist with 4.4b2?

I just stored a file successfully on a network storage. So WORKSFORME.

If this persists for you, please re-open with more details. Ideally maybe you can try to find reproduce steps.

OSX 10.10.1 LO Version: 4.5.0.0.alpha0+
Build ID: 629a705c127661111c54e14035b55850e36c2167
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2014-12-10_07:01:59
Locale: de_
Comment 5 retired 2014-12-10 11:44:05 UTC
oh and java 1.8 25