Crash in [@ libGLESv2_adreno.so]
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: towhite, Unassigned)
References
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/03ec7537-0e1a-4c55-b99b-ae6780240519
Reason: SIGSEGV / SEGV_MAPERR
Top 10 frames:
0 libGLESv2_adreno.so libGLESv2_adreno.so@0xecb94
1 libGLESv2_adreno.so libGLESv2_adreno.so@0x154167
2 libgsl.so libgsl.so@0x151382
3 libgsl.so libgsl.so@0xc2853
4 libc.so libc.so@0x79a69
5 libc.so libc.so@0xb20be
6 libc.so libc.so@0xb83ca
7 libc.so libc.so@0x8c579
8 libGLESv2_adreno.so libGLESv2_adreno.so@0xfde87
9 libGLESv2_adreno.so libGLESv2_adreno.so@0xaf415
Comment 3•4 months ago
|
||
:jnicol, do you have any idea what caused the crash?
Comment 4•4 months ago
|
||
The spike in this signature comes from bug 1895527, so this is replacing all the signatures in bug 1218607 (and other signatures that hadn't manually been added there.)
In terms of identifying and fixing the bugs, that's a lot more difficult. I imagine there are several root causes on a variety of devices, and without steps to reproduce it's not really actionable.
Updated•4 months ago
|
Updated•4 months ago
|
Comment 5•4 months ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 10 AArch64 and ARM crashes on release
:bhood, could you consider increasing the severity of this top-crash bug?
For more information, please visit BugBot documentation.
Comment 6•4 months ago
|
||
I think we should change the signatures so they include the calling frame. I believe we have that on dlls. What's the way to do that Will?
Comment 7•4 months ago
|
||
Jeff: Create a new bug with the specifics of what you're thinking and what it would look like, then we can figure out how to make it happen.
Comment 8•3 months ago
|
||
Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.
For more information, please visit BugBot documentation.
Updated•24 days ago
|
Description
•