Apache OpenOffice (AOO) Bugzilla – Issue 89137
OOo Aqua crashes as soon as "Open File" is selected
Last modified: 2008-11-19 13:30:20 UTC
Steps to reproduce: (1) open OO (defaults to new document) (2) Click on the "open file" icon or select the "File" ==> "open" menu Instead of giving me a file dialog to select a file to open, it crashes amd "Document Recovery" window pops up telling me that the new document (first default) will be recovered next time oo is opened. Here's a stack trace that it the tries to send to apple: Date/Time: 2008-05-07 12:25:47.218 -0700 OS Version: 10.4.11 (Build 8S2167) Report Version: 4 Command: soffice.bin Path: /Applications/OpenOffice.org.app/Contents/MacOS/soffice.bin Parent: WindowServer [70] Version: 3.0.0 (???) PID: 259 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0xa7d41b5e Thread 0 Crashed: 0 libuno_sal.dylib.3 0x002218ba rtl_ustr_shortenedCompareIgnoreAsciiCase_WithLength + 65 1 fps_aqua.uno.dylib 0x16c53262 component_getFactory + 23420 2 fps_aqua.uno.dylib 0x16c57461 component_getFactory + 40315 3 com.apple.AppKit 0x9346fcc9 -[NSNavDataSource displayStateForNode:] + 209 4 com.apple.AppKit 0x9345baa0 -[NSNavSidebarItemView isEnabled] + 146 5 com.apple.AppKit 0x9345c40f -[NSNavSidebarItemView updateTextColor] + 35 6 com.apple.AppKit 0x9345bea9 -[NSNavSidebarItemView setFrameSize:] + 170 7 com.apple.AppKit 0x9345d634 -[NSNavSidebarItemView setFrame:] + 250 8 com.apple.AppKit 0x9345cf55 -[NSNavSidebarView _layoutItemViewForWithItemHeight:allSidebarItemViews:] + 1170 9 com.apple.AppKit 0x9344db4f -[NSNavSidebarView tileIfNecessary] + 401 10 com.apple.Foundation 0x927f0237 _nsnote_callback + 230 11 com.apple.CoreFoundation 0x908563ce __CFXNotificationPost + 345 12 com.apple.CoreFoundation 0x9084db49 _CFXNotificationPostNotification + 600 13 com.apple.Foundation 0x927e87c8 -[NSNotificationCenter postNotificationName:object:userInfo:] + 121 14 com.apple.Foundation 0x927ef769 -[NSNotificationCenter postNotificationName:object:] + 55 15 com.apple.AppKit 0x9329090b -[NSView _postFrameChangeNotification] + 135 16 com.apple.AppKit 0x932ae9aa -[NSClipView setFrameSize:] + 210 17 com.apple.AppKit 0x932ae713 -[NSScrollView tile] + 3199 18 com.apple.AppKit 0x932ad875 -[NSScrollView _update] + 34 19 com.apple.AppKit 0x932ad84a -[NSScrollView resizeSubviewsWithOldSize:] + 150 20 com.apple.AppKit 0x9328d7cd -[NSView setFrameSize:] + 288 21 com.apple.AppKit 0x932ad5be -[NSScrollView setFrameSize:] + 432 22 com.apple.AppKit 0x932aebc5 -[NSView resizeSubviewsWithOldSize:] + 168 23 com.apple.AppKit 0x9328d7cd -[NSView setFrameSize:] + 288 24 com.apple.AppKit 0x933a3a49 -[NSSplitView adjustSubviews] + 1300 25 com.apple.AppKit 0x933ab966 -[NSSplitView resizeSubviewsWithOldSize:] + 190 26 com.apple.AppKit 0x9328d7cd -[NSView setFrameSize:] + 288 27 com.apple.AppKit 0x933ab888 -[NSSplitView setFrame:] + 257 28 com.apple.AppKit 0x9336be22 -[NSView resizeWithOldSuperviewSize:] + 451 29 com.apple.AppKit 0x932aebc5 -[NSView resizeSubviewsWithOldSize:] + 168 30 com.apple.AppKit 0x9328d7cd -[NSView setFrameSize:] + 288 31 com.apple.AppKit 0x93453a6a -[NSNavView tileVertically] + 556 32 com.apple.AppKit 0x93453d60 -[NSNavView resizeSubviewsWithOldSize:] + 34 33 com.apple.AppKit 0x9328d7cd -[NSView setFrameSize:] + 288 34 com.apple.AppKit 0x93392bde -[NSBox _tile:] + 1372 35 com.apple.AppKit 0x933c136c -[NSBox setFrameSize:] + 154 36 com.apple.AppKit 0x93456112 -[NSSavePanel(NSSavePanelLayout) _layoutViewsVerticallyAndResize] + 1534 37 fps_aqua.uno.dylib 0x16c4e2b9 component_getFactory + 3027 38 fps_aqua.uno.dylib 0x16c4e453 component_getFactory + 3437 39 fps_aqua.uno.dylib 0x16c4fc1d component_getFactory + 9527 40 libsfxmxi.dylib 0x01225a00 sfx2::FileDialogHelper::StartExecuteModal(Link const&) + 130 41 libsfxmxi.dylib 0x01225c7f sfx2::FileDialogHelper::LinkStubExecuteSystemFilePicker(void*, void*) + 407 42 libsfxmxi.dylib 0x01226dbc sfx2::FileDialogHelper::Execute(SvStringsDtor*&, SfxItemSet*&, String&, String const&) + 216 43 libsfxmxi.dylib 0x010207d4 SfxApplication::LoadTemplate(SfxObjectShellLock&, String const&, unsigned char, SfxItemSet*) + 13616 44 libsfxmxi.dylib 0x011ba7be SfxDispatcher::Execute(SfxExecuteItem const&) + 768 45 libsfxmxi.dylib 0x011baebf SfxDispatcher::_Execute(SfxSlotServer const&) + 759 46 libsfxmxi.dylib 0x011e624b SvxSearchItem::QueryValue(com::sun::star::uno::Any&, unsigned char) const + 89279 47 libsfxmxi.dylib 0x011e61fb SvxSearchItem::QueryValue(com::sun::star::uno::Any&, unsigned char) const + 89199 48 libvclmxi.dylib 0x01d2ef5d Window::~Window [in-charge]() + 23971 49 libvclmxi.dylib 0x01db8717 component_getFactory + 132779 50 libvclmxi.dylib 0x01b8a489 Application::Yield(bool) + 83 51 libvclmxi.dylib 0x01b8a520 Application::Execute() + 84 52 libsoffice.dylib 0x0008f321 0x78000 + 95009 53 libvclmxi.dylib 0x01b8fb8b InitVCL(com::sun::star::uno::Reference<com::sun::star::lang::XMultiServiceFactory> const&) + 1493 54 libvclmxi.dylib 0x01db7d56 component_getFactory + 130282 55 libvclmxi.dylib 0x01dbab50 SalGetDesktopEnvironment() + 5996 56 com.apple.AppKit 0x9326fa87 -[NSApplication run] + 547 57 com.apple.AppKit 0x932639c0 NSApplicationMain + 573 58 libvclmxi.dylib 0x01db96ee SalGetDesktopEnvironment() + 778 59 libvclmxi.dylib 0x01b8fc17 SVMain() + 17 60 libsoffice.dylib 0x000b9b60 soffice_main + 160 61 org.openoffice.script 0x00002bba main + 30 62 org.openoffice.script 0x0000252a start + 258 63 org.openoffice.script 0x00002451 start + 41
I'm having the same issue (also runing 10.4.11). Tested on 3.0.0 beta2 and rc1.
The (May 2008) steps to reproduce are vaguely familiar to me, I might have reported something similar (probably not identical) that seemed to affect OOo of that era _only after_ a crash … i.e., _only if_ invitation to recover was timely. nekobito, please, can you reproduce the symptoms in OpenOffice.org 3.0 Release Candidate 2 (build OOO300_m7)? That version or something more recent should be referenced from <http://blogs.sun.com/GullFOSS/>. I guess that to test: you might force OOo to quit, whilst it has open a new or previously saved text document with unsaved edits. If the issue persists then please change the 'Version:' here from 1.0.0 to match the version with which you're testing. Thanks Graham
I forced quit from RC 2 whilst editing a new document. Launched OOo. Declined the invitation to recover. When an empty text document appeared, I clicked the file menu but then decided to not use that option. Instead, I clicked on the 'Open' icon in the toolbar. The dialogue appeared, and I could dismiss the dialogue. No crash.
FWIW, I can reproduce this using too for RC2. If I follow the steps sketched by Graham Perrin, the application crashes when clicking the "open" icon on the OO toolbar. Stack trace is the same: Date/Time: 2008-09-29 19:20:17.747 +0200 OS Version: 10.4.11 (Build 8S2167) Report Version: 4 Command: soffice.bin Path: /Applications/OpenOffice.org.app/Contents/MacOS/soffice.bin Parent: soffice [515] Version: 3.0.0 (???) PID: 516 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0xa7d43b5e Thread 0 Crashed: 0 libuno_sal.dylib.3 0x00223116 rtl_ustr_shortenedCompareIgnoreAsciiCase_WithLength + 65 1 fps_aqua.uno.dylib 0x1953e246 component_getFactory + 23420 [snip]
Created attachment 56907 [details] Error i got while trying to restart my Mac because I couldn't make OO do anything afte the crash.
I tested with RC2 and I can reproduce the exact same error with exact same steps - and more. With this version, after the recovery, I don't get the Menu at the top anymore. I couldn't quit the application but couldn't, so I tried to force quit the application. It would not let me force quit no matter how many times I tried - and waited a long time. I had to hard reboot the Mac just to be able to start a new OO session. (Should this be another report?) I'm still running on 10.4.11. I can get he stack trace, if you need to see it, but it looks pretty much the same as before. ** I attached a picture thinking that it will go with this comment, but it didn't. The picture shows the message i got while trying to restart my mac but couldn't because soffice.bin would not force-quit. **
FYI: I also encountered the "force quit" doesn't work issue. A "killall -9 soffice.bin" from the terminal does a better job though (I don't know how force quit is implemented in os x).
Interesting enough, the crashes don't occur using another user account. Nekobito, can you verify this? Removing ~/Library/Application\ Support/OpenOffice.org/ doesn't help though, I still seeing the crashes in my own account.
See also issue 90437.
In September 2008 I wrote: > The (May 2008) steps to reproduce are vaguely familiar to me, I > might have reported something similar (probably not identical) > that seemed to affect OOo of that era _only after_ a crash … Ah, now I realise why I couldn't find my report in the openoffice.org area. http://bugzilla.neooffice.org/bug.php?op=show&bugid=3145 *** crash following cancellation of document recovery *** leads to http://bugzilla.neooffice.org/bug.php?op=show&bugid=3144 > soffice.bin crashes when applying a bullet, or > scrolling through a fonts menu After first pointing the finger of suspcion at APE, Silk and other hacks/enhancements, the bug there was closed with this note: > The fact that the crashing stopped after cleaning the font > caches and disabling certain fonts is consistent with the > location of the crash (the crash was occurring in an internal > Mac OS X function related to font cache management) so I think > we can conclude that you had a corrupt font or corrupt font > cache. Now, as I review my (11:23 AM 07-04-2008) note at http://bugzilla.neooffice.org/bug.php?op=show&bugid=3144 I wonder whether there was truly corruption, or whether there was simply some _discrepancy_ between a) fonts _actually cached on disk_ and b) applications' notions of what _might_ or_should_ be available from such caches -- bear in mind that a few days prior to the crashing behaviours, I had used Apple Font Book to weed supposedly duplicate fonts. (If my thoughts/expressions here are becoming fuzzy, sorry -- I'm not a developer!) Now, re-focusing on OOo: 1. does OOo keep its own cache of fonts? If so, then: 2. upon which sources are the OOo cache based? 3. is there maybe some discrepancy between what OOo _expects_ to find in cache(s), and what's _actually_ cached? In my experience, issues relating to fonts can manifest themselves in very unexpected ways... Regards Graham
Paying closer attention ... my contributions to this issue 89137 may be straying far from nekobito's original subject: > OO crashes as soon as "Open File" is selected If it's leading to a mixture of two or more distinct bugs, sorry!
Extra information: - Adding the Recovery.xcu file as described in issue 90437 doesn't solve the crash - When I open a file by clicking on it in "Finder", OO opens the document correctly without crashing. Regarding the font cache remark: Does OS X maintains font caches on a per user basis?
In response to kgadeyne (comment on Fri Oct 3 17:47:13): Yes, I didn't think of trying as a different user, but you're right! I was running OOo as a user with no administrative rights and it was crashing. Today, I ran it as a user with admin rights and it does not have an issue opening a file.
> Does OS X maintains font caches on a per user basis? I'm no expert on the internals of Mac OS X but for myself, I find at least 24 M apparently cached at /private/var/folders/HR/HRdTSV2kEwO7D2VzvzQ-m+++GmE/-Caches-/com.apple.ATS @ kgadeyne : Somewhere within your own /private/var/folders/ you may find a path that relates to your Mac OS X user ID. The path may not be named in a way that indicates your ID, but if you browse each path you'll probably find one that presents (to you) more than the other paths. = Partial transcript from a Terminal window session = [macbookpro03-centrim:~] gjp22% ls -l /private/var/folders total 0 drwxr-xr-x 3 root wheel 102 11 Jul 23:37 0I drwxr-xr-x 3 root wheel 102 7 Jul 12:05 15 drwxr-xr-x 3 root wheel 102 8 Jul 03:58 8a drwxr-xr-x 3 root wheel 102 7 Jul 15:05 GC drwxr-xr-x 3 root wheel 102 16 Jul 10:58 HR drwxr-xr-x 3 root wheel 102 7 Aug 21:02 Jp drwxr-xr-x 3 root wheel 102 7 Jul 23:27 Mh drwxr-xr-x 3 root wheel 102 7 Jul 15:03 Ph drwxr-xr-x 3 root wheel 102 17 Sep 15:49 Xv drwxr-xr-x 12 root wheel 408 4 Sep 07:30 zz [macbookpro03-centrim:~] gjp22% ls -hrlt /private/var/folders/HR/HRdTSV2kEwO7D2VzvzQ-m+++GmE/-Caches-/com.apple.ATS total 48216 -rw-r--r-- 1 gjp22 staff 105K 20 Sep 04:58 User.fcache -rw-r--r-- 1 gjp22 staff 156K 25 Sep 17:05 Local.fcache -rw-r--r-- 1 gjp22 staff 162K 25 Sep 17:05 System.fcache -rwxr--r-- 1 gjp22 staff 22M 8 Oct 22:29 annex_aux -rw-r--r-- 1 gjp22 staff 734K 9 Oct 05:18 font [macbookpro03-centrim:~] gjp22% du -h /private/var/folders/HR/HRdTSV2kEwO7D2VzvzQ-m+++GmE/-Caches-/com.apple.ATS 24M /private/var/folders/HR/HRdTSV2kEwO7D2VzvzQ-m+++GmE/-Caches-/com.apple.ATS
> @ kgadeyne : > Somewhere within your own > /private/var/folders/ > you may find a path that relates to your Mac OS X user ID. Hmm, I haven't got a /private/var/folders directory $ ll /private/var/folder* ls: /private/var/folder*: No such file or directory I cleaned up files owned by myself in /private/var/tmp , but that doesn't help either.
This problem most likely has the same root cause as issue 93828. Where crash reports submitted? What where the "reportids" in the acknowledging email?
From my side, there's rr4myuc, rm4myuc, rk4myuc, r4pxyuc, rypxyuc. Unfortunately, the bug also caused a "window focus" problem, i.e. I could almost never fill in report details :-(
@kgadyne: thanks for the reportids, they all show that same problem (internal reminder: osxstackid7614) which are probably solved in CWS macrestart2. It is targeted for OOo301. In the meantime please use the workaround I mentioned in issue 93828: disable native dialogs by enabling Tools->Options->Office->General->OpenSaveDialogs->UseOwnDialog @tm: I still suggest to reproduce the problem here so the fix for CWS 93828 can be confirmed to work for this problem too
hdu wrote: > @kgadyne: thanks for the reportids, they all show that same > problem (internal reminder: osxstackid7614) which are probably > solved in CWS macrestart2. Re highlights and sticky notes at http://www.diigo.com/annotated/ff23c417255b05143a8d98cf6897f0f0 http://www.diigo.com/annotated/ae21c6f831d19e87fdfb65a675cd02e9 http://www.diigo.com/annotated/d8ad77a15e5d0f28a54aa16d5bb11f17 http://www.diigo.com/annotated/11051a3263d23479b7145351cc0b569e -- various indications of inability to force quit -- is the solution mentioned here 'CWS macrestart2' relevant to issues with force quit? (Will separate tickets be appropriate?)
The reportids confirmed the suspicion that this problem is identical to the one solved with the fix for issue 93828. *** This issue has been marked as a duplicate of 93828 ***
@grahamperrin: the problems you mentioned are unrelated to this issue. AFAIK also the CWS macrestart2 doesn't have to do with these problems. Separate issues seem appropriate. Other than that I'm closing this resolved issue.