Closed Bug 551242 Opened 10 years ago Closed 10 years ago

Hang (caught by hang detector) with flash and alt key


(Core :: Plug-ins, defect)

Windows 7
Not set



Tracking Status
status1.9.2 --- .4-fixed


(Reporter: benjamin, Assigned: jimm)



(Whiteboard: [fixed-lorentz])


(1 file, 2 obsolete files)

Hang, caught by the hang detector, with flash context menu and the alt key:


* load a youtube video, e.g.
* right-click the video to show the flash context menu
* hit the alt key a few times

In release builds the hang detector kicks in and kills off the plugin process after 10 seconds. This may be related to the topcrash bug 536666 / bug 546035, I first tried these steps because of a comment in one of those crash reports.
I have this in recording, haven't diagnosed yet.
Child is processing Windows messages, ends up at:

>	_DefWindowProcA@16()	
 	[Frames below may be incorrect and/or missing, no symbols loaded for npswf32.dll]	
 	mozilla::plugins::PluginInstanceChild::PluginWindowProc(hWnd=0x000d02a0, message=0x00000105, wParam=0x00000012, lParam=0xc0380001)	C++

message 0x105 is WM_SYSKEYUP

Parent is sending an unrelated RPC message (NPP_WriteReady). AFAICT we're not hooking whatever window receives WM_SYSKEYUP for deferred message processing, thus the deadlock.
Assignee: nobody → jmathies
Turns out that the context menu isn't necessary, all you have to do is give the plugin focus (by tabbing to it or clicking on it) and then hit "alt" to get the hang.
Jim, this is probably more important than the foxit crash.
Blocks: LorentzBeta1
So, flash hands wm_syskeyup to def wnd proc, which in turn generates a wm_syscommand message that gets sent to the top level window. That in current nightly builds is handed to def wnd proc as well, which generates all sorts of secondary events. With the child waiting on the return, the first ipc call from parent hangs.

I tried a couple things hoping for a quick fix - deferring wm_syscommand helped but since child is held waiting, we can still get deadlocks if ipc network is heavy. Also tried a combo replymessage call / deferred wm_syscommand, but I still managed get a hang on repeated key strokes. So there's still something going on here that's unknown, will dig into it more tomorrow morning.
Summary: Hang (caught by hang detector) with flash context menu and alt key → Hang (caught by hang detector) with flash and alt key
Attached patch fix (obsolete) — Splinter Review
Handling this the same way we handle activate events did the trick. Also included is a little bit of cleanup in IPCWindowProcHandler. Also, I kept the two if statements separate because i wanted specific comments for each.
Comment on attachment 431689 [details] [diff] [review]

argh, two patches combined in one.
Attachment #431689 - Attachment is obsolete: true
Attached patch fix (obsolete) — Splinter Review
Attached patch fixSplinter Review
some additional cleanup.
Attachment #431690 - Attachment is obsolete: true
Attachment #431711 - Flags: review?(bent.mozilla)
Comment on attachment 431711 [details] [diff] [review]

Nit, fix the indentation here, should be 2 spaces.

+      GetPropW(mWnd, L"PluginInstanceParentProperty")) {
+      ReplyMessage(0);
Attachment #431711 - Flags: review?(bent.mozilla) → review+
Closed: 10 years ago
Resolution: --- → FIXED
Blanket approval for Lorentz merge to mozilla-1.9.2
a=beltzner for - please make sure to mark status1.9.2:.4-fixed
You need to log in before you can comment on or make changes to this bug.