Bug 50710 - Application crashes
Summary: Application crashes
Status: RESOLVED DUPLICATE of bug 49942
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.4 release
Hardware: x86-64 (AMD64) macOS (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-05 00:40 UTC by berend
Modified: 2013-12-05 15:48 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
The Mac OSX crash log (81.24 KB, text/plain)
2012-06-05 00:40 UTC, berend
Details

Note You need to log in before you can comment on or make changes to this bug.
Description berend 2012-06-05 00:40:46 UTC
Created attachment 62558 [details]
The Mac OSX crash log

The application crashes after a short time. It doesn't seem to matter what one is doing:
* viewing a .docx document
* edit a new document
* insert a table
* paste a graphic
* do nothing

I have attached the crash log.
Comment 1 Julien Nabet 2012-06-05 15:02:11 UTC
Did you try with a brand new LO profile (see http://wiki.documentfoundation.org/UserProfile) ?
Could you try with accessibility features disabled ? (see https://bugs.freedesktop.org/show_bug.cgi?id=47368)
Comment 2 Roman Eisele 2012-06-19 00:16:31 UTC
An additional question:
which MacOS X version do you use (e.g., 10.6.x or 10.7.x)? This is also important.
Comment 3 Roman Eisele 2012-06-19 00:18:29 UTC
(In reply to comment #2)
> An additional question:
> which MacOS X version do you use (e.g., 10.6.x or 10.7.x)? This is also
> important.

Sorry, this was a thumb question -- I saw the crash log too late. From the log file, it is clear: Mac OS X 10.7.4 (11E53).

But please answer Julien Nabet's questions; they are really important.
Comment 4 Roman Eisele 2012-07-21 11:08:29 UTC
(Yet another attempt to get the missing information)


Hello berend@tty.nl,
thank you very much for your bug report!

I am sorry that LibreOffice crashes for you. However, the same things which
cause LibreOffice to crash for you work fine on many other machines (e.g., on
my one; I have just tried again with LibreOffice 3.5.5.3, German langpack
installed, on MacOS X 10.6.8: no crashes).

So we need to find out what makes the difference, i.e. why LibreOffice crashes
in your installation. The first things to check are:

1) Can you please try running LibreOffice with a brand new LibreOffice user
profile (see http://wiki.documentfoundation.org/UserProfile)? This seems to
heal many serious problems (cf. e.g. bug 51323).

2) Do you have any accesibility features enabled? Apple’s accessibility
features like "VoiceOver" or "Enable access for assistive devices", which get
enabled in "System Preferences > Universal Access" (in German:
"Bedienungshilfen"), are known to cause many crashes in LibreOffice (see bug
47368). So please try to disable any accesibility features.

3) Do you have installed any window management/user interface utilities/apps
for MacOS X like 
* Moom      (see bug 42014)
* Cinch     (see bug 51791)
* RightZoom (see bug 51686)
* ShiftIt   (see bug 52147)?
All these and many similar utilities rely heavily on accessibility issues and
therefore cause LibreOffice to crash. So please check if you have installed any
utility of this kind and try to disable it (or to add LibreOffice to the list
of excluded applications for the utility, if there is such a thing).

Thank you very much for trying this out (and please report the results here,
too)!
Comment 5 Roman Eisele 2012-08-16 10:07:36 UTC
Because we did not get an answer to the important questions (comment #1 and comment 4) for about two months, I see two possibilities to handle this bug:
-- to let it linger in the bug base for some more time and then to close it
   as RESOLVED/INVALID; but this would help nobody;
-- to mark it as a duplicate of bug 47368, because the original description
   (pseudo-random crashes on many different actions with LibO on MacOS X)
   reminds us heavily of this famous bug and its many duplicates.
Of course, it would be *much* better if the original reporter could confirm if this bug is really a duplicate of bug 47368; but obviously we don't get an answer from him/her.

Therefore, I mark this report as a duplicate of bug 47368 for now, because it is *probably* a duplicate of that bug. Everybody, please feel free to re-open this bug report if you can find any additional evidence about it which proves that it is a different issue. Thank you!

*** This bug has been marked as a duplicate of bug 47368 ***
Comment 6 Roman Eisele 2012-09-18 16:31:58 UTC
Mac Accessibility Related Bugs Survey Results
---------------------------------------------

This is a mixed bug report about various ways to crash LibreOffice, so it is difficult to deal with it. It is even not sure if the crashes mentioned here are really related to Mac OS accessibility features in comment 4 and comment 4 (although it seems probable).

Therefore I have to limit my survey to the Mac OS X crash log attached to this report. Two ideas about it:

1) As the thread 0 stack trace tells us, the crash obviously happened when closing a window (line 3: “Window:~Window()”), and obviously it was a dialog window with tabs (line 7: “AbstractTabDialog_Impl::~AbstractTabDialog_Impl()”), and, to be more concrete, the visible tab was the border style settings tab (line 4: “SvxBorderTabPage::~SvxBorderTabPage()”; cf.
  http://opengrok.libreoffice.org/xref/core/cui/source/inc/border.hxx
).

2) The stack trace, line 2, also shows that there was a call to
   Window::CallEventListeners(unsigned long, void*)
AFTER the window’s destructor was called (“Window::~Window()”, line 3).

Both observations together seem to suggest to a simple-minded bugwrangler like me that this is more or less the same bug as the issue (I) in bug 47368 (see
   https://bugs.freedesktop.org/show_bug.cgi?id=47368#93
and ff.). This bug was fixed by Tor Lillqvist’s patch
http://cgit.freedesktop.org/libreoffice/core/commit/?id=9b9d45e35103e6884e0a87c35c07c74899f40614
This patch will appear in LibreOffice 3.6.2 and 3.7.0.

Therefore I hope that the present bug was also fixed by the commit mentioned above, and therefore I let this bug marked as a duplicate of bug 47368 which was fixed by that commit.


@ berend@tty.nl:
If you can still reproduce the crashes mentioned here with LibreOffice 3.6.2 or newer, please report that!

But it would be even more helpful if you could please
-- create a new bug report for each way to crash LibreOffice (or at least
   for two or three of them, if there are too much ;-).
-- In each of these reports, please describe in as much details as possible
   how to reproduce the crash (step by step from starting the application
   on, even mouse click by mouse click:
   sorry, but this is really necessary!),
-- To each of these reports, please attach the Mac OSX crash log
   created on exactly that kind of crash.

This would be very very helpful! It would allow us to reproduce the problem exactly, and only this makes it possible to fix it.

Thank you very much!
Comment 7 Roman Eisele 2012-09-19 15:02:02 UTC
Mac Accessibility Related Bugs Survey Results -- Update
-------------------------------------------------------

Sorry for the ongoing revision, but I keep learning while sorting all the bug reports ;-)

In my previous comment, I have already argued that the crash on which the attached log file was created must have happened when closing a dialog window with the border style settings tab (used, e.g., in the “Paragraph” dialog of Writer or in the “Cell” dialog of Calc, both available via the “Format” menu).

Now comparing the stack trace to the stack traces of other bugs, I notice an important similarity of the present stack trace to the stack trace for bug 49942, which is about changing the border style of tables in Writer -- bingo!

Therefore I conclude that the both bugs are related, i.e. that the crash reported in the present bug report has very probably the same roots as the crash reported in bug 49942. (The issue (I) in bug 47368, which I mentioned in my previous comment, is indeed very similar, but shows a slightly different stack trace including more calls to explicit accessibility-related stuff.)

So I mark this bug as a duplicate of bug 49942 this time. Let’s proceed with the latter, because any progress about bug 49942 will very probably also fix the present issue.
Comment 8 Roman Eisele 2012-09-19 15:02:19 UTC

*** This bug has been marked as a duplicate of bug 49942 ***