To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=111106 Issue #|111106 Summary|vcl: crash in X11SalData::XIOErrorHdl after SVData is |freed Component|gsl Version|DEV300m77 Platform|All URL| OS/Version|Linux Status|NEW Status whiteboard| Keywords| Resolution| Issue type|PATCH Priority|P3 Subcomponent|code Assigned to|pl Reported by|cmc
------- Additional comments from [email protected] Fri Apr 23 10:46:12 +0000 2010 ------- As seen in https://bugzilla.redhat.com/show_bug.cgi?id=584198 we have a stack where we crash in X11SalData::XIOErrorHdl due to some IOError in the shutdown in at-spi which happens well after our vcl svdata and friends have been destroyed. I can't reproduce this of course, but I can easily replicate it by forcing an XIOError in at-spi's shutdown with a11y enabled. Its surely a most extreme edge-case but here's a patch to save and restore the XIOHandler on ctor and dtor of SalXLib. And while I'm at it, I think we don't need to set X11SalData::XIOErrorHdl via XSetErrorHandler in the gtk/kde/kde4 ctors as one is already pushed up in their parent SalXLib class --------------------------------------------------------------------- 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]
