GNOME Bugzilla – Bug 558028
atkbridge makes firefox remote client crash during shutdown/atexit
Last modified: 2014-11-15 00:56:46 UTC
In ubuntu/intrepid we get duplicate crash reports for firefox-3.0; this turned out to be caused by access to a corrupted *environ in atk-brige's atexit hook. See: https://bugs.edge.launchpad.net/ubuntu/+source/at-spi/+bug/278095 Is there any use for doing a getenv in shutdown and exit instead of remembering its value during module_initialization?
Created attachment 121405 [details] [review] do not access environ during shutdown/atexit from ubuntu bug: https://bugs.edge.launchpad.net/ubuntu/+source/at-spi/+bug/278095/comments/12
anyone could review this patch please?
Some of test code in at-spi use this env.
well ... accessing environ isnt good in at-exit. please remove that test then.
also more details if you have concerns with a patch would be appreciated.
Actually I plan to change the atexit way to gtk_quit_add way in the next release.
[Resetting QA Contact to newly introduced "at-spi-maint@gnome.bugs". Reason: So far it was impossible to watch changes in at-spi bug reports without following all the specific persons (Li Yuan, Bill Haneman, Jeff Wai, ...) and also their activity outside of at-spi reports. IMPORTANT: Anyone interested in following all bug activity (including all maintainers) must watch the "at-spi-maint@gnome.bugs" dummy user by adding it to the 'Users to watch' list under Preferences->Email preferences. This is also the default procedure nowadays in GNOME when setting up new products.]
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
I'm going to go ahead and close this because it concerns a very old version. Feel free to open a new bug if the problem persists.