680641 - Firefox hanges, Plugin-container process crashes

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Plug-ins, defect)

Description

[thirumalaivelu]

User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.94 Safari/535.1

Steps to reproduce:

- open a page that loads a custom NPAPI plugin.
- open another page that loads a different plugin like flash, pdf.

Stack trace:

020ff7bc 77d2564c 75fde921 00000100 020ff810 ntdll!KiFastSystemCallRet
020ff7c0 75fde921 00000100 020ff810 020ff804 ntdll!ZwRemoveIoCompletion+0xc
020ff7ec 0f9fb66a 00000100 020ff838 020ff810 KERNELBASE!GetQueuedCompletionStatus+0x29
020ff818 0f9fb610 005174c0 ffffffff 00000000 xul!base::MessagePumpForIO::GetIOItem+0x37 [e:\builds\moz2_slave\rel-m-rel-w32-bld\build\ipc\chromium\src\base\message_pump_win.cc @ 528]
020ff840 0fa131c5 ffffffff 00000000 0f9dacd1 xul!base::MessagePumpForIO::WaitForIOCompletion+0x24 [e:\builds\moz2_slave\rel-m-rel-w32-bld\build\ipc\chromium\src\base\message_pump_win.cc @ 499]
020ff84c 0f9dacd1 005174c0 005174c0 0053b208 xul!base::MessagePumpForIO::WaitForWork+0x1c [e:\builds\moz2_slave\rel-m-rel-w32-bld\build\ipc\chromium\src\base\message_pump_win.cc @ 493]
020ff860 0fa29ae0 0053b208 020ff8e8 00000000 xul!base::MessagePumpForIO::DoRunLoop+0x68 [e:\builds\moz2_slave\rel-m-rel-w32-bld\build\ipc\chromium\src\base\message_pump_win.cc @ 477]
020ff87c 0fa29af2 020ff8e8 0fa0544a 020ff8e8 xul!base::MessagePumpWin::RunWithDispatcher+0x31 [e:\builds\moz2_slave\rel-m-rel-w32-bld\build\ipc\chromium\src\base\message_pump_win.cc @ 54]
020ff884 0fa0544a 020ff8e8 890b4e3c 0053b208 xul!base::MessagePumpWin::Run+0xc [e:\builds\moz2_slave\rel-m-rel-w32-bld\build\ipc\chromium\src\base\message_pump_win.h @ 78]
020ff8bc 0fa0541b 00000001 75fd6800 00000000 xul!MessageLoop::RunHandler+0x21 [e:\builds\moz2_slave\rel-m-rel-w32-bld\build\ipc\chromium\src\base\message_loop.cc @ 203]
020ff8d8 0fa053de 00000000 00000000 1041c7d4 xul!MessageLoop::Run+0x15 [e:\builds\moz2_slave\rel-m-rel-w32-bld\build\ipc\chromium\src\base\message_loop.cc @ 177]
020ff9a0 0fa302a8 763c1114 0053b208 020ff9f0 xul!base::Thread::ThreadMain+0x6e [e:\builds\moz2_slave\rel-m-rel-w32-bld\build\ipc\chromium\src\base\thread.cc @ 159]
020ff9a4 763c1114 0053b208 020ff9f0 77d3b429 xul!`anonymous namespace'::ThreadFunc+0x9 [e:\builds\moz2_slave\rel-m-rel-w32-bld\build\ipc\chromium\src\base\platform_thread_win.cc @ 27]
020ff9b0 77d3b429 0053b208 7fd3d4ed 00000000 kernel32!BaseThreadInitThunk+0xe
020ff9f0 77d3b3fc 0fa3029f 0053b208 00000000 ntdll!__RtlUserThreadStart+0x70
020ffa08 00000000 0fa3029f 0053b208 00000000 ntdll!_RtlUserThreadStart+0x1b

dump file attached


Actual results:

After opening the second page, a new plugin-container gets created and terminated in a loop, the main browser window appears to hang.


Expected results:

Firefox should not have hung.

Comment 1

[(mostly gone) XtC4UaLL [:xtc4uall]]

Can you test against more recent Firefox Versions like 6, 7 Beta or a Nightly?

Comment 2

[thirumalaivelu]

The issue is repro'd with the latest FF 6.x also

Comment 3

[(mostly gone) XtC4UaLL [:xtc4uall]]

Can you give any Information regarding to making the Issue reproducible?

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to XtC4UaLL [:xtc4uall] from comment #3)
> Can you give any Information regarding to making the Issue reproducible?

Comment 5

[Mats Palmgren (inactive)]

> open a page that loads a custom NPAPI plugin

I suspect this the essential part for reproducing the bug - would it possible
to share that plugin so that we can analyze the problem?

Comment 6

[Wayne Mery (:wsmwk)]

(In reply to Mats Palmgren [:mats] from comment #5)
> > open a page that loads a custom NPAPI plugin
> 
> I suspect this the essential part for reproducing the bug - would it possible
> to share that plugin so that we can analyze the problem?