Closed
Bug 1207844
Opened 9 years ago
Closed 4 years ago
crash in nsAppShell::ProcessNextNativeEvent
Categories
(Firefox for Android Graveyard :: General, defect, P5)
Tracking
(firefox44 ?)
RESOLVED
INCOMPLETE
Tracking | Status | |
---|---|---|
firefox44 | --- | ? |
People
(Reporter: david.weir, Unassigned)
References
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is
report bp-dd89961e-d431-4025-9646-5fe652150923.
=============================================================
Steps to reproduce
1 visit https://www.virgo-networks.co.uk/billing/knowledgebase.php?action=displaycat&catid=5
The browser crashed
Reporter | ||
Updated•9 years ago
|
Product: Toolkit → Firefox for Android
Reporter | ||
Updated•9 years ago
|
status-firefox44:
--- → ?
Comment 1•9 years ago
|
||
2 crashes over the last 28 days for all Firefox for Android crash reports.
Comment 2•9 years ago
|
||
I hit this also while scrolling down a bugzilla page
https://crash-stats.mozilla.com/report/index/ad74c944-f517-4e29-a565-5e1302150924
Comment 3•6 years ago
|
||
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195
Needinfo :susheel if you think this bug should be re-triaged.
Priority: -- → P5
Comment 4•4 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•