Issue 106292 - Crashreporter broken on Mac
Summary: Crashreporter broken on Mac
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOO320m2
Hardware: Mac Mac OS X, all
: P2 Trivial (vote)
Target Milestone: OOo 3.2
Assignee: Stephan Bergmann
QA Contact: issues@framework
Keywords: regression
Depends on:
Blocks: 99999
  Show dependency tree
Reported: 2009-10-26 15:05 UTC by thorsten.martens
Modified: 2009-11-13 12:41 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description thorsten.martens 2009-10-26 15:05:32 UTC
After document-recovery no crashreporter appears when clicking on "Next"-button.
Office just starts normally with recovered document.
Comment 1 carsten.driesner 2009-10-26 15:07:30 UTC
cd->pl: This is a Mac specific problem. Could you please take over.
Comment 2 mdxonefour 2009-10-26 15:22:49 UTC
MD: Adjusting prio, keywords, blocks and cc list.
Comment 3 philipp.lohmann 2009-10-26 16:15:13 UTC
I don't even have an idea where the crash reporter code resides.
Comment 4 philipp.lohmann 2009-10-26 16:49:33 UTC
pl->sb: kso told me, the crash reporter is now your's ? cd's tip about the
crashrep module does not seem to be current however; as far as I can see that
would be gtk code for all unx platforms (including mac).
Comment 5 Stephan Bergmann 2009-10-26 17:49:26 UTC
Comment 6 Stephan Bergmann 2009-10-27 14:54:23 UTC
AFAIK, OOo crash handling on Mac OS X has always been fragile in that a
crash-causing signal is not necessarily delivered to the sal signal handler,
which would cause a ~/.crash_report_unsent to be written, which in turn would
cause the Document Recovery wizard on the (automatic) OOo re-start to have the
Error Report page which this issue states is missing.

@tm:  As this is stated to be a regression, please provide an exact scenario
that fails in OOO320m2 and succeeds in some other version (which one?).
Comment 7 mdxonefour 2009-10-27 15:49:03 UTC
@sb: It was me who added the keyword regression. I already saw the crash
reporter on MacOS a couple of times since I use a Mac at all. Since I was
starting to use OOO320 builds, the office crashed a couple of times, but I never
saw the crash reporter showing up with any of the OOO320 builds.

So I just tried to force a SEGV by using kill command. By this I can't force the
crash reporter to show up. Not with OOO320m2 and not with an old OOo 3.1.1 final

As said in the beginning of this comment I would have sweared I saw the crash
reporter in the past already on my Mac!? :(
Comment 8 Stephan Bergmann 2009-10-27 16:49:59 UTC
@md:  In OOo on Mac OS X, signal handling (and thus crash reporting) is no
longer working reliably as soon as an in-process JVM is started (which, e.g.,
happens when you execute certain "File - Wizards" or "Tools - Macros" entries).
 This is a known problem, see issue 92720.  Please remove the regression keyword
again if not appropriate.
Comment 9 Stephan Bergmann 2009-10-28 17:14:38 UTC
@tm:  Please provide further information as requested in <#desc7> (or close as
duplicate of issue 92720 if appropriate).
Comment 10 thorsten.martens 2009-11-12 13:21:46 UTC
TM->SB: please have a look at #106678 (occurs on 320m4). Simple way to let the
office crash (new text document, view/toolbars/bullets & numbering, click on
very right button, select option tabpage) ->crash.
The first time, no recovery dialog appears when office crashes, but recovery
starts afterwards. As I clicked on Next-button for the crashreporter, no
crashreporter appears but office starts normally. 
The second time (I just let the office crash in the same way) an office
recovery-dialog appears after the crash, the doccument was recovered during
startup AND the crashreporter comes up.

Strange behaviour, one time it works and one time it doesn't. Please have a look
and mention if this is still a duplicate or a different new behaviour.

Thanks in advance
Comment 11 Stephan Bergmann 2009-11-13 12:40:14 UTC

What I could experience with OOO320m4 OOo is that "Bullets and
Numbering - Options" causes a crash, first " Document Recovery"
dialog (informing about the crash) appears, OOo restarts, second "
Document Recorvery" dialog appears, correctly with all dialog pages to recover
the documents and send the report.  => WORKSFORME

If you then do "Bullets and Numbering - Options" in the automatically restarted
OOo, OOo will hang completely.  This is issue 106355.
Comment 12 Stephan Bergmann 2009-11-13 12:41:22 UTC