Closed
Bug 949548
Opened 10 years ago
Closed 10 years ago
crash in @0x0 | mozilla::layers::Axis::DisplacementWillOverscroll(float)
Categories
(Core :: Panning and Zooming, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 936500
People
(Reporter: tnguyen, Unassigned)
References
Details
(Keywords: crash, regression, Whiteboard: [b2g-crash])
Crash Data
This bug was filed from the Socorro interface and is report bp-babfd905-34d0-4db1-bc25-304e42131212. ============================================================= I encountered this issue while using the Browser App with WiFi connected. After loading some links, the device crashed. I will investigate further and provide better STR. Repro Steps: 1) Updated Buri to Master M-C BuildID: 20131212040203 2) Connect device to WiFi 3) Navigate into the Browser App 4) Begin browsing by loading several websites Actual: Device crashed Expected: Device doesn't crash
Updated•10 years ago
|
Component: General → Panning and Zooming
Product: Firefox OS → Core
Updated•10 years ago
|
Keywords: regression
Whiteboard: [b2g-crash]
This bug was filed from the Socorro interface and is report bp-95b0be1e-b111-4798-b99e-7d94a2131212. ===================================================== I had the same crash today on the 1.3 Aurora Moz RIL, when I quickly scrolled a page down Device: Buri 1.3 Aurora Moz RIL BuildID: 20131210004003 Gaia: 3452fbdb5e1bed0cd27cc6173136537a03e8072f Gecko: e0c328d99742 Version: 28.0a2 Firmware Version: v1.2_20131115
Reporter | ||
Updated•10 years ago
|
status-b2g-v1.3:
--- → affected
status-firefox29:
--- → affected
Comment 2•10 years ago
|
||
kats - any ideas on what might be causing this crash? It looks like a regression on 1.3. Is there enough info here to make this actionable?
Flags: needinfo?(bugmail.mozilla)
Comment 3•10 years ago
|
||
Based on the stack I suspect this might have been introduced in bug 839911 and may be fixed by Chris' patch to fix FlingAnimation on bug 936500. If that doesn't happen then we might need STR to diagnose it.
Flags: needinfo?(bugmail.mozilla)
Comment 5•10 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #4) > After bug 936500, we should try to retest this. After bug 936500 lands I mean.
Comment 6•10 years ago
|
||
So far the data is consistent with bug 936500 fixing this bug. There are no crashes on 29 after that bug landed, but there are still crashes on 28. That bug was just uplifted to 28 so we should see the crashes there die off as well.
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Updated•10 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•