To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112605
------- Additional comments from c...@openoffice.org Thu Jun 24 08:25:37 +0000 2010 ------- My own 2 cents is that I'd like to see a much longer stack to see some more details of this particular example, i.e. --num-callers=50 or something. We get quite a few crash-on-shutdown traces in fedora as our crash-reporting infrastructure is global over all apps and over their entire lifetime. And they fall into two main categories. I've seen ones like this one with a11y shutdown where the a11y shutdown and release of uno references is called effectively from "spi_atk_bridge_exit_func" which nightmarishly is called from atexit from the accessibility libs which makes avoiding this tricky. The other family is due to the current cppu shutdown being crippled to attempt to "leak" resources to avoid accessing dead ones, but this has the side effect of not calling the dtors which cleanly bring down the remotebridge reader/writer threads leaving them generally blocked on mutexes and then after those global mutex gets destroyed on main processes exit the threads unblock and trample all over the corrupt corpse of OOo. The common case is unopkg crashes which are no fault of unopkg. See issue 107490 for some thoughts on fixing that up. --------------------------------------------------------------------- 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: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
