Closed Bug 726425 Opened 8 years ago Closed 3 years ago

[adbe 3202915] Plugin hang in base::MessagePumpForUI::ProcessNextWindowsMessage after returning from welcome screen

Categories

(Core :: Plug-ins, defect, critical)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: andreasjunghw, Unassigned)

References

Details

(Keywords: hang, reproducible, Whiteboard: [STR in comment 3])

Crash Data

I got this hang twice now after doing basically the same thing:
1) Opened ca. 10-15 YouTube videos (to watch later)
   this will bring plugin-container's memory usage to
   working set: 300MB virtual size: 700MB
2) left the computer; I have the option "On resume, display Welcome Screen" 
   activated, so when I come back to my PC I'm asked to enter my password.
3) I login again and notice Firefox hangs; After a few seconds Firefox reacts
   again and I get the plugin crashed message.

bp-b58a5121-2c5c-4290-9b3c-bb9272120211
bp-2c428dc9-bd25-44ba-8234-b8ec72120211
Blocks: 560549
Crash Signature: [@ hang | NtUserPeekMessage ]
Keywords: hang
It's a Flash hang but without anything related to Flash in the stack.
In the stack, there's uxtheme.dll 6.0.2900.5512 that's a patched version of the official MS dll, so it's probably the cause.
Severity: normal → critical
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Plugin hang after returning from welcome screen [@ hang | NtUserPeekMessage ] → Plugin hang after returning from welcome screen [@ hang | NtUserPeekMessage ] with UxTheme.dll 6.0.2900.5512
(In reply to Scoobidiver from comment #1)
> In the stack, there's uxtheme.dll 6.0.2900.5512 that's a patched version of
> the official MS dll, so it's probably the cause.

If you mean patched as in modified to allow custom themes then you are wrong.

The file was never modified and is the original windows xp service pack 3 file (or a later security patch level; I don't know and the Microsoft website is totally useless if you try to search for file versions...).

Process Explorer also agrees that the file is an unmodified Microsoft DLL.
Keywords: topcrash
Summary: Plugin hang after returning from welcome screen [@ hang | NtUserPeekMessage ] with UxTheme.dll 6.0.2900.5512 → Plugin hang after returning from welcome screen [@ hang | NtUserPeekMessage ]
Crash Signature: [@ hang | NtUserPeekMessage ] → [@ hang | NtUserPeekMessage ] [@ hang | NtUserPeekMessage | NtUserPeekMessage]
Depends on: 720655
Crash Signature: [@ hang | NtUserPeekMessage ] [@ hang | NtUserPeekMessage | NtUserPeekMessage] → [@ hang | NtUserPeekMessage ] [@ hang | NtUserPeekMessage | NtUserPeekMessage | base::MessagePumpForUI::ProcessNextWindowsMessage()]
Summary: Plugin hang after returning from welcome screen [@ hang | NtUserPeekMessage ] → Plugin hang in base::MessagePumpForUI::ProcessNextWindowsMessage after returning from welcome screen
Crash Signature: [@ hang | NtUserPeekMessage ] [@ hang | NtUserPeekMessage | NtUserPeekMessage | base::MessagePumpForUI::ProcessNextWindowsMessage()] → [@ hang | NtUserPeekMessage ] [@ hang | NtUserPeekMessage | _PeekMessage] [@ hang | NtUserPeekMessage | NtUserPeekMessage | base::MessagePumpForUI::ProcessNextWindowsMessage()]
I found a page where I was able to reproduce the issue every time I tried.

STR:
1) Open http://www.fileformat.info/info/unicode/font/fontlist.htm?text=%E2%99%A1+-+WHITE+HEART+SUIT+%28U%2B2661%29
2) Wait until the screensaver appears / Windows locks the screen
3) Move the mouse so that the welcome screen is displayed
4) Log in again
5) Firefox hangs, after waiting for some time the crashed plugin message is displayed.

Tested with:
Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120330 Firefox/14.0a1
Adobe Flash Player 11,1,102,62
Windows XP SP3

Crash reports:
https://crash-stats.mozilla.com/report/index/bp-5fd439aa-30c3-437d-8f5f-e44cb2120331
https://crash-stats.mozilla.com/report/index/bp-464e850d-e139-4b19-8f01-491b82120331
I can't reproduce on Windows 7 in the trunk.
Keywords: reproducible
Still crashes after update to:
Adobe Flash Player 11,2,202,228

bp-f4905447-1e28-477c-8cd3-26d042120331
bp-076f85ba-7af9-4857-824a-60cce2120331

STR see comment 3
Whiteboard: [STR in comment 3]
Crash Signature: [@ hang | NtUserPeekMessage ] [@ hang | NtUserPeekMessage | _PeekMessage] [@ hang | NtUserPeekMessage | NtUserPeekMessage | base::MessagePumpForUI::ProcessNextWindowsMessage()] → [@ hang | NtUserPeekMessage ] [@ hang | NtUserPeekMessage | _PeekMessage] [@ hang | NtUserPeekMessage | NtUserPeekMessage | base::MessagePumpForUI::ProcessNextWindowsMessage()] [@ hang | NtUserPeekMessage | NtUserPeekMessage | NtUserPeekMessage ]
i'm also not able to reproduce the issue:  
system - windows xp sp3 Flash Player 11,2,202,235...
also, cannot reproduce on XP SP3 with Firefox 10 and 11,1,102,63 ...
Adding qawanted to try the STR in comment 3 on Windows XP.
Keywords: qawanted
In addition to the STR in comment 3, let's wait 10-20 minutes after the screen locks before unlocking again. Also please change the hang pref - go to about:config and change dom.ipc.plugins.timeoutSecs to 15. Thanks!
our corresponding internal bug is #3202915 to help diagnose this issue...
Summary: Plugin hang in base::MessagePumpForUI::ProcessNextWindowsMessage after returning from welcome screen → [adbe 3202915] Plugin hang in base::MessagePumpForUI::ProcessNextWindowsMessage after returning from welcome screen
Trying to test this now with the exact configuration and steps noted in comment 3 with the timeout modification in comment 10.
(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #12)
> Trying to test this now with the exact configuration and steps noted in
> comment 3 with the timeout modification in comment 10.

Unable to reproduce...
(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #13)
> (In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #12)
> > Trying to test this now with the exact configuration and steps noted in
> > comment 3 with the timeout modification in comment 10.
> 
> Unable to reproduce...

Maybe add a step 1b) Interact with the flash plugin / click on it; it seems to me that the bug is more likely to occur if the flash plugin is the focused element when the computer locks the screen.

Also note that I can't verify with Windows XP and the newest nightly if / how often the bug still occurs, because the computer I used to verify the STR is broken.

I also get the bug on a Windows Vista Notebook from time to time, but the bug seems to happen a lot less frequently on Windows Vista. (Maybe different STR would be needed to be able to reproduce it reliably on Windows Vista.)
https://crash-stats.mozilla.com/report/index/bp-a42fd34b-026c-4da1-9fdd-5ba362120706

Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0

Firefox 14 beta 11 crashed on a Windows XP SP 2 machine with Flash 11 .3. In the moment of the crash I was watching a video on YouTube, had one trailer running on IMDB and two other tabs opened. I changed the focus from the YouTube Video to another tab, Firefox froze and after that the Flash plug-in crashed. 
I could not reproduce the crash afterwards.
Keywords: topcrash
We also have experienced the hang in a different way, while developing our own plugin. It caused when the firefox is resized/relocated by resizing/relocating windows taskbar.
MessagePumpForUI::ProcessNextWindowsMessage::PeekMessageW then never returns in our plugin container process. SetWindow message is never received, while Firefox.exe waits for the response to this message and also hangs.
(tested WinXP/Win7/Win8 with FF 14 and FF 15).
Mozilla/5.0 (Windows NT 5.1; rv:27.0) Gecko/20100101 Firefox/27.0
Build ID: 20130922030201

I could not reproduce the issue on Windows XP SP3 on the latest Nightly using Adobe Flash 11.8.800.168 and following all the suggestions from Comment 3, 10 and 14. For now, I'm removing the QAWANTED keyword, please re-add it if anything else is needed from the QA side.

The Socorro reports still indicates a pretty high volume of crashes for the second and third signatures:
- [@ hang | NtUserPeekMessage | _PeekMessage]: 1479 on Firefox 23.0.1 RC, 1300 on Firefox 24 beta, 83 on Firefox 24 RC, 116 on Firefox 25b1.

- [@ hang | NtUserPeekMessage | NtUserPeekMessage | base::MessagePumpForUI::ProcessNextWindowsMessage()]: 3473 on Firefox 23.0.1RC, 128 on Firefox 24RC, 160 on Firefox 25b1.
Keywords: qawanted
Crash Signature: [@ hang | NtUserPeekMessage ] [@ hang | NtUserPeekMessage | _PeekMessage] [@ hang | NtUserPeekMessage | NtUserPeekMessage | base::MessagePumpForUI::ProcessNextWindowsMessage()] [@ hang | NtUserPeekMessage | NtUserPeekMessage | NtUserPeekMessage ] → [@ hang | NtUserPeekMessage ] [@ hang | NtUserPeekMessage | _PeekMessage] [@ hang | NtUserPeekMessage | NtUserPeekMessage | base::MessagePumpForUI::ProcessNextWindowsMessage()] [@ hang | NtUserPeekMessage | NtUserPeekMessage | NtUserPeekMessage ] [@ h…
Resolving old bugs which are likely not relevant any more, since NPAPI plugins are deprecated.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.