Nightly native crash
Categories
(Firefox for Android :: Crash Reporting, defect)
Tracking
()
People
(Reporter: anil, Unassigned)
Details
User Agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Mobile Safari/537.36
Steps to reproduce:
Firefox Nightly often crashes when navigating to a webpage. This happens on the majority of websites
This only started with the latest release.
Actual results:
Crash, the app closes
The only information is this in the crashes page
d4169a5d-ddec-460b-bb5e-259f8199bc7f
<native crash>
<native crash>
It's so bad I had to use chrome to file the bug.
130.0a1 (Build #2016034751), hg-69a2460cfcb3+
GV: 130.0a1-20240726035627
AS: 130.20240724050232
|
||
Comment 2•11 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Fenix::Crash Reporting' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
I can replicate this on https://www.nytimes.com/2024/07/27/us/politics/elon-musk-kamala-harris-deepfake.html, when navigating via hyperlink from a post on Hacker News. (https://news.ycombinator.com/item?id=41090459)
Visiting the webpage normally through the NYT homepage does not exhibit this behavior, oddly enough.
130.0a1 (Build #2016034751), hg-69a2460cfcb3+
GV: 130.0a1-20240726035627
AS: 130.20240724050232
2024-07-26T07:41:34.889371823
|
||
Updated•11 months ago
|
|
|
||
Comment 5•11 months ago
|
||
Please update your Nightly build. There was briefly one Nightly release that triggered crashes, but it has been fixed in 130.0a1 20240726152430.
Yes, this is fixed now.
In the future, is there anything I can do to get proper call stacks?
The other crash I saw happened at the same time, but that one is a dupe of https://bugzilla.mozilla.org/show_bug.cgi?id=1848134
And appears to be downstream of this crash if I'm understanding correctly
|
|
||
Comment 7•11 months ago
•
|
||
(In reply to anil from comment #6)
Yes, this is fixed now.
In the future, is there anything I can do to get proper call stacks?
The crash report should include the relevant stack trace. Do you not see it at about:crashes ?
The fact that I don't see any Android platform among 3k+ crash reports is very suspicious though... Your report here is a proof that the crash also affects Android, so I would have expected at least some Android reports.
EDIT: I filtered by Firefox; if I include Fenix I can see that there are even more crashes associated with this issue. In fact two-thirds of the 10k crashes are on Android.
The other crash I saw happened at the same time, but that one is a dupe of https://bugzilla.mozilla.org/show_bug.cgi?id=1848134
Bug 1848134 is independent of this crash, but might offer some insight in why the crash report is missing (or not).
The only info in about:crashes is the words <native crash> (also in the original post)
I can give you more details about the notification crash after it, but that one really looks similar to the one I just linked
Oh sorry even I misunderstood as the URL auto complete misled what I was looking at. I have no submitted crash reports.
My unsubmitted crash reports do not include this bug. I only see it if I go to settings ->about -> crashes
Description
•