I haven't spent any time tracking this down yet, but on my dev box, todays nightly emerge run hung/stuck forever with the last output being the install phase of nspluginwrapper with glibc being unhappy about it -- not sure if this is specific to my box or something unique about the latest ebuild bump: >>> Completed installing nspluginwrapper-1.4.4-r1 into /var/tmp/portage/www-plugins/nspluginwrapper-1.4.4-r1/image/ strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment usr/lib64/nspluginwrapper/x86_64/linux/npconfig usr/lib64/nspluginwrapper/x86_64/linux/npwrapper.so usr/lib64/nspluginwrapper/x86_64/linux/npplayer usr/lib64/nspluginwrapper/i386/linux/npviewer.bin usr/lib64/nspluginwrapper/i386/linux/libnoxshm.so >>> Installing (4 of 10) www-plugins/nspluginwrapper-1.4.4-r1 * Removing wrapper plugins... *** glibc detected *** nspluginwrapper: double free or corruption (out): 0x0000000000631b50 ***
I get the same error. It seems plugin listing and auto discovery options cause the error. The process hangs there (according to gdb, at function __lll_lock_wait_private function of libc) and needs to be killed. $ nspluginwrapper -l -v" /usr/lib/firefox/plugins/npwrapper.libflashplayer.so Original plugin: //opt/Adobe/flash-player32/plugin/libflashplayer.so Plugin viewer: /usr/lib64/nspluginwrapper/i386/linux/npviewer Wrapper version string: 1.4.4-1 *** glibc detected *** nspluginwrapper: double free or corruption (out): 0x0000000001eee920 *** $ nspluginwrapper -v -a -u Auto-update plugins from /usr/lib/mozilla/plugins Looking for plugins in /usr/lib/mozilla/plugins Auto-update plugins from /usr/lib64/mozilla/plugins Looking for plugins in /usr/lib64/mozilla/plugins Auto-update plugins from /usr/lib/firefox/plugins Looking for plugins in /usr/lib/firefox/plugins Update plugin /usr/lib/firefox/plugins/npwrapper.libflashplayer.so NPAPI plugin //opt/Adobe/flash-player32/plugin/libflashplayer.so is already installed system-wide, removing wrapper Remove plugin /usr/lib/firefox/plugins/npwrapper.libflashplayer.so *** glibc detected *** nspluginwrapper: double free or corruption (out): 0x0000000000b00950 *** Wheras the follwing command succesds $ nspluginwrapper -v -u /usr/lib/firefox/plugins/npwrapper.libflashplayer.so Update plugin /usr/lib/firefox/plugins/npwrapper.libflashplayer.so NPAPI plugin //opt/Adobe/flash-player32/plugin/libflashplayer.so is already installed system-wide, removing wrapper Remove plugin /usr/lib/firefox/plugins/npwrapper.libflashplayer.so
Interesting, could you please post emerge --info I am going to add upstream to the CC on this to see if they have any insight.
Can you run the command under valgrind? There's a memory problem, so it may give something useful. I've rarely had much luck with gdb in such cases, as the offending clobber tends to happen earlier than it's detected. If it comes from listing and auto-discovery, my guess would be that this comes from calling dlclose in is_wrapper_plugin. Many libraries are buggy and cannot be safely unloaded; if you look at just about any browser, they intentionally leak plugin handles on Linux. You may have a plugin installed which loads a buggy library. (For instance, if you have kopete installed, you get a skypebuttons.so plugin which pulls in Qt. On dlclose, you get a spurious pthread_key_delete(0). I don't think the fix for that is landing until 4.8, but I could be wrong.) I removed a similar call in nspluginplayer before. I'll do the same here for the next release. (That code also shouldn't dlopen everything, or at least do so less frequently, but that's a much more involved fix to a very nasty file.)
Created attachment 285893 [details] emerge --info output
Created attachment 285895 [details] valgrind output for 'valgrind nspluginwrapper --list'
Yeah, I bet it's the dlclose thing. Does it still happen if you apply this patch? https://github.com/davidben/nspluginwrapper/commit/f3c2b2d1f5ee558ad2f3c7830821d591c8a0f440
(In reply to comment #6) > https://github.com/davidben/nspluginwrapper/commit/f3c2b2d1f5ee558ad2f3c7830821d591c8a0f440 Yes the patch fixes the issue.
Created attachment 285903 [details] patch file from git
Fixed in www-plugins/nspluginwrapper-1.4.4-r2 with the attached patch.
