[OpenIndiana-discuss] Adobe Flash crashes with Firefox 20 & 21 on OI_151a8

[Milan Jurik]

Hi Bryan,

I know about it for long time. It could be because some libs were 
updated and even if they did not change public ABI, flash plugin can use 
something specific. Or something else. I have no plans to investigate. 
Adobe stopped to support our platform some time ago and there are 
different things which would be nice to solve instead of hunting the 
root cause in old vulnerable binary blob.

Best regards,

Milan

On 31.05.2013 19:11, Bryan N Iotti wrote:
> Hi all,
>
> I can't seem to be able to view YouTube videos on OI_151a8 using
> Firefox 20 or 21 and Adobe Flash 11.2.
>
> When I go to the page for a video, any video apparently, Firefox
> seems to load the page and then hangs for 20 seconds before reporting
> that the Flash plugin crashed.
>
> I have core dumps from the plugin-container process.
>
> My knowledge of mdb is very limited, but this is the kind of feedback
> I'm getting:
>
>> ::status
>
> debugging core file of plugin-containe (32-bit) from Spook
>
> file: /export/home/ghost/Apps/firefox/plugin-container
>
> initial argv:
>
> /home/ghost/Apps/firefox/plugin-container
> /home/ghost/.mozilla/plugins/libflash
>
> threading model: native threads
>
> status: process terminated by SIGSEGV (Segmentation Fault), addr=14
>
>
>> ::stack
>
> 0xf8195dc2(efd06000, 280, b4, 280, 280, efd63010)
>
> 0xf81745e9(8046250, 280, b4, f6bceeb0, 280, 280)
>
> 0xf7e02645(f1197480, 8046250, 0, b4)
>
> 0xf7b7d181(f700b070, fed80000, f6bcef88, f79aa20e)
>
> 0xf79aa236(f700b078, fe8c2000, 210, fed1e6e6)
>
> 0xf79aa290(f700b078, 62, 8, fed85840)
>
> 0xf79a9f50(f700b078, fed80000, f6bcefe8, fed1f3ee)
>
> libc_hwcap1.so.1`_thrp_setup+0x9b(f9a92240)
>
> libc_hwcap1.so.1`_lwp_start(f9a92240, 0, 0, 0, 0, 0)
>
>
> If I try to walk the affected threads, I get this:
>
>> 0xf8195dc2::walk thread | ::findstack
>
> stack pointer for thread 1: 8046198
>
> [ 08046198 libc_hwcap1.so.1`yield+0x15() ]
>
>   080461e8 libc_hwcap1.so.1`cond_signal+0x18c()
>
>   08046208 0xf79aa372()
>
>   08046428 0xf7c94b77()
>
>   08046468 0xf7ab4d49()
>
>   080464f8 0xf7abef48()
>
>   080465a8 0xf7ac0f39()
>
>   08046688 0xf7de5132()
>
>   08046718 0xf7da51cf()
>
>   080467d8 0xf7da71db()
>
>   08046888 0xf79adbb1()
>
>   08046948 0xf79a125c()
>
>   08046968 libglib-2.0.so.0.2800.6`g_timeout_dispatch+0x20()
>
>   080469f8 libglib-2.0.so.0.2800.6`g_main_dispatch+0x1df()
>
>   08046a18 libglib-2.0.so.0.2800.6`g_main_context_dispatch+0x93()
>
>   08046a78 libglib-2.0.so.0.2800.6`g_main_context_iterate+0x3a8()
>
>   08046ab8 libglib-2.0.so.0.2800.6`g_main_context_iteration+0x7f()
>
>   08046b18
>
>
> 
> libxul.so`__1cEbaseQMessagePumpForUIRRunWithDispatcher6Mpn0ALMessagePumpIDelegate_p
>
>   n0BKDispatcher__v_+0x6e()
>
>   08046b38
>
>
> 
> libxul.so`__1cEbaseQMessagePumpForUIDRun6Mpn0ALMessagePumpIDelegate__v_+0x17()
>
>   08046b68 libxul.so`__1cLMessageLoopDRun6M_v_+0x35()
>
>   08047818 libxul.so`XRE_InitChildProcess+0x3a7()
>
>   08047848 main+0x3e()
>
>   0804786c _start+0x7d()
>
>
> <WAY MORE>
>
>
> Now, what should I do?
>
> Does anyone want a copy of the core files so they can dissect them
> more accurately?
> Should I also post this to oi-dev?
>
> Bryan