Closed Bug 678818 Opened 8 years ago Closed 8 years ago
"ASSERTION: Window still registered with device motion" and crash
Steps to reproduce: 1. Load the testcase. 2. Quit Firefox. (Or, close the tab and click the MP button in about:memory.) Result: An assertion fails during GC: ###!!! ASSERTION: Window still registered with device motion.: '!mHasDeviceMotion', file dom/base/nsGlobalWindow.cpp, line 1039 Which is soon followed by: Invalid read of freed memory [@ nsDeviceMotion::DeviceMotionChanged] in order to make a virtual function call. (Beware: bp-4cdef108-d00e-4b39-8e21-d86152110813 makes it look like a null deref, but it is actually a more serious bug.)
We are starting up the device motion after Cleanup() is called. This patch ensure that the device motion is disabled during the global window destructor.
Assignee: nobody → doug.turner
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Comment on attachment 553001 [details] [diff] [review] patch v.1 Approved for Aurora (Update 8) and Beta (Update 7.) Please land it as soon as possible.
http://hg.mozilla.org/releases/mozilla-aurora/rev/f717ca3b24e7 This patch doesn't apply to beta ...
Doug, can you merge this fix to beta? Probably some silly context differences that causes it not to apply... And we're running out of time for 7...
qa- as no QA fix verification needed
Whiteboard: [sg:critical?] → [sg:critical?][qa-]
You need to log in before you can comment on or make changes to this bug.