Closed Bug 985967 Opened 10 years ago Closed 10 years ago

High memory usage and crash after loading a gamepad demo in private window

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

29 Branch
All
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bmaris, Unassigned)

References

Details

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0

Steps to reproduce:
1. Start Firefox
2. Open a new private window
3. Load gamepad demo: http://people.mozilla.com/~tmielczarek/combat/
4. Press some buttons on the controler

Expected results: Demo works as expected.

Actual results: After a few seconds the memory usage jumps to 2GB and climbs up to 4GB, Firefox is not responding and crashes. Sometimes Firefox only remains in not responding mode without crashing.

Crash reports:
bp-731143a0-b9c6-4276-b4a6-4a3672140320
bp-f1fa3296-9aa1-42dd-8a6c-f56372140320
bp-07eaab59-4449-43b8-b7bb-ac8c82140320
bp-96ac1bb8-bbde-47a0-8f0c-221842140320
bp-a7c230cc-284e-4457-87bf-36d4a2140320

Notes:
1. The crash only reproduces if I use two controllers.
2. With Nightly from 2013-12-08 (when bug 878828 was pushed), I get this crash: bp-5c4ee358-5275-4a47-8314-925d22140307.
3. Also reproduced the hang but not the crash in Windows 8.1 64bit but harder (I opened some more tabs with that demo and also restarted the browser a few times from Developer Toolbar). No crashes on Ubuntu or Mac OS X.
4. Reproduced with a Xbox 360 controller and Logitech Gamepad F310.
5. If I try to reproduce this on Nightly I encounter bug 980876.
I can easily reproduce this crash with Firefox 29 beta 1 by navigating to http://people.mozilla.com/~tmielczarek/combat/ and press a button on the controller. Reproduced on 3 different Window 7 64bit machines.
Crash reports:
bp-96ac1bb8-bbde-47a0-8f0c-221842140320
bp-07eaab59-4449-43b8-b7bb-ac8c82140320
bp-50fc349e-13fb-4531-8055-44f7c2140321

I couldn't reproduce it with http://luser.github.io/gamepadtest/ demo. I've encountered once the Unresponsive script alert (1 out of 4 tries).

The odd fact is that this crash is also reproducible with Nightly from 2013-12-08 (when bug 878828 landed): bp-f1a3a25d-eebd-4d7f-aa7d-86e4c2140321

Could this be related with Windows OS updates from the last days/weeks? It doesn't make any sense with the presence of the crash on Nightly from 2013-12-08. Ted, any thoughts on this?
Flags: needinfo?(ted)
I've tried reproducing this on both Nightly and 29 Beta 1 with no luck. I followed the STR from comment 0 on a fresh profile:
1) Start firefox
2) Open a new private browsing window
3) Load http://people.mozilla.com/~tmielczarek/combat/
4) Press buttons on two connected gamepads.

Am I missing something?
Flags: needinfo?(ted)
Hello
I have try to reproduce the bug with 2 gamepads in private browsing under Firefox 31.0a1 (x86_64) ( 21/03/2014 nightly) with windows7 64bit version (sp1) but COULDN'T reproduce crash.
I did some more digging and I retested on a new machine with Windows 7 x64, and I could not reproduce using STR from comment 0, but instead I was able to get a irrecoverable hang using this steps:

1) Start Firefox
2) Load http://people.mozilla.com/~tmielczarek/combat/ and press some buttons
3) Open private window, load http://people.mozilla.com/~tmielczarek/combat/ and press some buttons
4) Options/Privacy and set 'Firefox will' to 'Never remember history' then restart
5) Load http://people.mozilla.com/~tmielczarek/combat/ and press some buttons

If it does not work this way restart browser from Developer Toolbar and repeat step 2. After the hang I could reproduce the crash with ease but not with the same steps all the time. Restarting browser seams to help crash FF.
I get the same result when if I save a page with gamepad events (such as the test page at http://luser.github.io/gamepadtest/) and double click it so it's the first page that firefox opens, or if I set such a page to be the browser homepage and restart the browser.

After crashing, I get repeat crashes when I reopen firefox, as it tries to reload the session with a gamepad page.

Again, this occurs only when using two or more controllers - and if any other page loads before the controller page, everything works normally.

Sometimes (however not always), the first controller will show up in the gamepad test page as having a large number of axes, and no buttons. In these cases, it is only when i press a button on the misrepresented gamepad that the browser hangs and crashes.

I uploaded a picture of this to http://sciencevsmagic.net/gamepadbug.png - please note that both controllers are actually the same, and are usually recognized as such.
I was not able to reproduce this anymore on Firefox 29 beta 8 using three different machines with Windows 7 64bit and 32bit. Probably patch from bug 980876 fixed this. 

Nico can you please see if you can still reproduce the issue on Firefox 29 beta 8?
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/29.0b8-candidates/build1/win32/en-US/

If you can't reproduce I will close this issue as Worksforme.
Flags: needinfo?(nico.disseldorp)
I can't reproduce the issue anymore with FF29 beta 8.
Flags: needinfo?(nico.disseldorp)
Thanks Nico.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.