This bug was filed from the Socorro interface and is report bp-13181cb4-c816-4639-9a72-08e122121115 . ============================================================= reports - ttp://tinyurl.com/afq7d33 https://crash-stats.mozilla.com/report/index/13181cb4-c816-4639-9a72-08e122121115 This is in MetroFirefox, and is currently the top crasher, although we don't have a lot of data yet.
This might be caused by something down in the winrt widget layer since the line the crash occurs on is nsIntPoint tmpPoint = aEvent->widget->WidgetToScreenOffset();
Null widget? Some bug how events are dispatched?
(In reply to Olli Pettay [:smaug] from comment #2) > Null widget? Some bug how events are dispatched? Probably. Odd though since the up times are all over the place. Something like this is more likely at startup. We'll have to audit all of our event sending.
Assignee: nobody → netzen
Jim you may want to take a stab at this, I reviewed the code but could not find the reason.
Assignee: netzen → nobody
Whiteboard: [metro-it1][LOE:1][metro-mvp] → [metro-it1][metro-it2][LOE:1][metro-mvp]
We haven't seen this since the 11-14 build, so I'm not too worried. Actually what worries me more is that we have people who are still on the 11-14 build. :) I think there's a bug filed someplace on improving update rates by doing updates in metro vs. desktop.
(In reply to Jim Mathies [:jimm] from comment #5) > We haven't seen this since the 11-14 build, so I'm not too worried. It still occurs and is #2 top crasher in MetroFirefox: https://crash-stats.mozilla.com/report/list?signature=nsEventStateManager%3A%3AFillInEventFromGestureDown%28nsMouseEvent*%29
The stacks here appear to be in the desktop product.
OS: Windows 8 Metro → Windows 7
Crash Signature: [@ nsEventStateManager::FillInEventFromGestureDown(nsMouseEvent*)] → [@ nsEventStateManager::FillInEventFromGestureDown(nsMouseEvent*)] [@ nsEventStateManager::FillInEventFromGestureDown]
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Last Resolved: 3 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.