Created attachment 363924 [details] emerge --info www-client/chromium When I try to play a Flash video on youtube.com or other site, I got a "Shockwave Flash player crashed" error, and I got a kernel complain: chrome[2872]: segfault at 28 ip 00007fe8887b3ae8 sp 00007fffccc637e0 error 4 in chrome[7fe88565a000+4ff1000] chrome[2968]: segfault at 28 ip 00007fb2dcc85ae8 sp 00007fff71c72a10 error 4 in chrome[7fb2d9b2c000+4ff1000] chrome[2987]: segfault at 28 ip 00007f9ed36c4ae8 sp 00007fff759c2720 error 4 in chrome[7f9ed056b000+4ff1000] I did not have this issue with Chromium 31.
What plugin is that?
(In reply to Jeroen Roovers from comment #1) > What plugin is that? That was the message I saw when the segmentation fault happens. I think it is something like http://www.adobe.com/products/shockwaveplayer.html. But on my system, I only installed adobe/flash-player. I guess they are equivalent.
I am seeing the same behavior. The most bizarre thing is that it does not appear to affect every flash video, but it does seem to be largely reproducible when there is one that causes the crash. For example this URL repeatedly causes the plugin to crash on my box: http://www.artofmanliness.com/2009/03/05/how-to-sharpen-a-pocket-knife/ Also built with chromium-32.0.1700.19 and adobe-flash-11.2.202.327.
(In reply to Xi from comment #2) > (In reply to Jeroen Roovers from comment #1) > > What plugin is that? > > That was the message I saw when the segmentation fault happens. I think it > is something like http://www.adobe.com/products/shockwaveplayer.html. But on > my system, I only installed adobe/flash-player. I guess they are equivalent. Did you mean www-plugins/adobe-flash ? You should really check that because that plugin is probably incompatible with chromium. Install www-plugins/chrome-binary-plugins instead and please report back with enough information.
(In reply to Jeroen Roovers from comment #4) > (In reply to Xi from comment #2) > > (In reply to Jeroen Roovers from comment #1) > > > What plugin is that? > > > > That was the message I saw when the segmentation fault happens. I think it > > is something like http://www.adobe.com/products/shockwaveplayer.html. But on > > my system, I only installed adobe/flash-player. I guess they are equivalent. > > Did you mean www-plugins/adobe-flash ? You should really check that because > that plugin is probably incompatible with chromium. Install > www-plugins/chrome-binary-plugins instead and please report back with enough > information. Yes, I meant www-plugins/adobe-flash. I just emerged chrome-binary-plugins, and I can see flash now. I think the problem is resolved for me. But does the chrome-binary-plugins is a complete replacement for the adobe-flash? If not, I think it is just a walk around.
Maybe chromium has a plugin blacklist that libflashplayer.so could be added to?
(In reply to Xi from comment #5) > Yes, I meant www-plugins/adobe-flash. I just emerged chrome-binary-plugins, > and I can see flash now. I think the problem is resolved for me. But does > the chrome-binary-plugins is a complete replacement for the adobe-flash? If > not, I think it is just a walk around. chrome-binary-plugins only works with chromium; if you are using other browsers (like Firefox), then adobe-flash is your only option. (In reply to Jeroen Roovers from comment #6) > Maybe chromium has a plugin blacklist that libflashplayer.so could be added > to? I'm not sure. However, I believe Chromium will be dropping support for all NPAPI plugins at some point in the not-so-distant future.
(In reply to Mike Gilbert from comment #7) > I'm not sure. However, I believe Chromium will be dropping support for all > NPAPI plugins at some point in the not-so-distant future. It will, see http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html Xi, could you obtain a stack trace of the plugin process using instructions from https://code.google.com/p/chromium/wiki/LinuxDebugging ?
(In reply to Paweł Hajdan, Jr. from comment #8) > (In reply to Mike Gilbert from comment #7) > > I'm not sure. However, I believe Chromium will be dropping support for all > > NPAPI plugins at some point in the not-so-distant future. > > It will, see > http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html > > Xi, could you obtain a stack trace of the plugin process using instructions > from https://code.google.com/p/chromium/wiki/LinuxDebugging ? I read the wiki, but I am dumb with gdb...sorry. I launched with this command: chrome --plugin-launcher='xterm -e gdb' Then I go to http://v.youku.com/v_show/id_XNjQ0NDE1ODIw.html, a Chinese video website. Below are what I saw in the console. LaunchProcess: failed to execvp: xterm [45:45:1207/114621:ERROR:webplugin_delegate_proxy.cc(321)] Plug-in crashed on start [12316:12342:1207/114628:ERROR:audio_manager_base.cc(422)] Not implemented reached in virtual std::string media::AudioManagerBase::GetDefaultOutputDeviceID() ATTENTION: default value of option force_s3tc_enable overridden by environment. [12316:12337:1207/114628:ERROR:form_data.cc(108)] Bad pickle of FormData, no version present LaunchProcess: failed to execvp: xterm [72:72:1207/114641:ERROR:webplugin_delegate_proxy.cc(321)] Plug-in crashed on start LaunchProcess: failed to execvp: xterm [72:72:1207/114641:ERROR:webplugin_delegate_proxy.cc(321)] Plug-in crashed on start LaunchProcess: failed to execvp: xterm [72:72:1207/114642:ERROR:webplugin_delegate_proxy.cc(321)] Plug-in crashed on start [12316:12334:1207/114708:ERROR:audio_manager_base.cc(422)] Not implemented reached in virtual std::string media::AudioManagerBase::GetDefaultOutputDeviceID() I don't know if it would be useful. If you can provide me more detailed instruction, I would like to give another try.
(In reply to Xi from comment #9) > LaunchProcess: failed to execvp: > xterm > > I don't know if it would be useful. If you can provide me more detailed > instruction, I would like to give another try. Please install xterm and try again. When you see a window with (gdb) prompt, type "run" (+ enter). Then when you see a crash type "bt". If you have trouble getting the backtrace out, try just logging your gdb session, see e.g. http://stackoverflow.com/questions/1707167/how-extract-text-from-gdb (set logging file, set logging on, then bt).
(In reply to Paweł Hajdan, Jr. from comment #10) > (In reply to Xi from comment #9) > > LaunchProcess: failed to execvp: > > xterm > > > > I don't know if it would be useful. If you can provide me more detailed > > instruction, I would like to give another try. > > Please install xterm and try again. > > When you see a window with (gdb) prompt, type "run" (+ enter). Then when you > see a crash type "bt". > > If you have trouble getting the backtrace out, try just logging your gdb > session, see e.g. > http://stackoverflow.com/questions/1707167/how-extract-text-from-gdb (set > logging file, set logging on, then bt). I emerged 'xterm' and tried again. But I did not see the gdb prompt. Maybe I am using the wrong commend? I am not sure if I should debug a plugin, or a renderer. Can you help?
(In reply to Xi from comment #11) > I emerged 'xterm' and tried again. But I did not see the gdb prompt. Maybe I > am using the wrong commend? I am not sure if I should debug a plugin, or a > renderer. What did you see in the console?
(In reply to Paweł Hajdan, Jr. from comment #12) > (In reply to Xi from comment #11) > > I emerged 'xterm' and tried again. But I did not see the gdb prompt. Maybe I > > am using the wrong commend? I am not sure if I should debug a plugin, or a > > renderer. > > What did you see in the console? Pretty much the same as I posted in Comment 9.
Given that chromium-34 now stable dropped support for NPAPI, I'm closing this. See the following for more info: http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html https://groups.google.com/a/chromium.org/d/msg/chromium-dev/xEbgvWE7wMk/D_07G2lftacJ http://www.chromium.org/developers/npapi-deprecation
