To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=108545 Issue #|108545 Summary|crash handling fails on Windows with recent JVMs Component|porting Version|DEV300m69 Platform|PC URL| OS/Version|Windows, all Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|sb Reported by|sb
------- Additional comments from [email protected] Thu Jan 21 13:08:36 +0000 2010 ------- On Windows, the OOo crash handling apparently is disabled after a sufficiently recent JVM is instantiated in-process (i.e., once any Java code has been executing within OOo). Sun HotSpot JVM 1.5.0_06 is known to be good, while JVM 1.6.0_11 and 1.6.0_16 are known to fail. The effect is that upon an OOo crash no OOo Defect Report dialog (informing the user that OOo crashed) comes up, OOo is not automatically restarted, and after manual restart no OOo Error Reporting dialog (guiding the user to send data about the crash) comes up; document recovery (after manual restart) is not affected. The reason is that the JVM apparently no longer passes unhandled structured exceptions to the unhandled exception filter that was set (in sal/osl/w32/signal.c) before the VM is created. I filed a corresponding Sun-internal issue (b6918421) against the HotSpot JVM. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
