GNOME Bugzilla – Bug 415389
crash because NPPVpluginKeepLibraryInMemory is broken in gecko
Last modified: 2007-03-10 12:44:58 UTC
Steps to reproduce: See http://bugzilla.gnome.org/show_bug.cgi?id=353503 Stack trace: Other information: patch to not use NPPVpluginKeepLibraryInMemory is coming
Created attachment 84094 [details] [review] use dlopen to make dbus-glib resident and drop NPPVpluginKeepLibraryInMemory setting
You should dlclose the handle. Otherwise this looks fine to me.
Created attachment 84125 [details] [review] with dlclose
Looks fine to me. Bastien, since this should fix the epiphany topcrash bug 353503, I think we should try to get this into 2.18.0.
I'd rather keep the NPPVpluginKeepLibraryInMemory as well, in case Gecko fixes it...
(In reply to comment #5) > I'd rather keep the NPPVpluginKeepLibraryInMemory as well, in case Gecko fixes > it... I guess you mean to #if 0 that instead of removing it? I don't see why we'd need to put it back though. It was only introduced because libdbus-glib cannot be reloaded; and so I'd argue that making that library (and only that library) resident was actually the right thing to do.
Freeze break requested.
i still don't totally get how this will fix bug 353503...
It will 'fix' it because the bug is triggered by the plugin's native window not being destroyed correctly, when the plugin is 'cached' with NPPVpluginKeepLibraryInMemory. So with this patch, totem won't trigger that bug anymore (but the gecko bug will still exist).
Code freeze break agreed. Could you please commit Christian?
I had to adapt the patch, as it is against 2.16.x. Committed to trunk and gnome-2-16. 2007-03-09 Bastien Nocera <hadess@hadess.net> * browser-plugin/totemPlugin.cpp: * browser-plugin/totemPluginGlue.cpp: Patch from Alexander Sack <asac@jwsdot.com> to keep the dbus-glib library in memory, to avoid crashes when switching themes (Closes: #415389)
what happens to bug 353503 now?
the mozilla bug https://bugzilla.mozilla.org/show_bug.cgi?id=359870 will stay open. For bug 353503 I would suggest to close it (after a while catching late duplicates maybe?) as the crash should be gone with totem update.