Open
Bug 1438485
Opened 7 years ago
Updated 2 years ago
Crash in dalvik-main space (deleted)@0xa7c2cf5
Categories
(Core :: Gecko Profiler, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox58 | --- | unaffected |
firefox59 | --- | unaffected |
firefox60 | --- | fix-optional |
People
(Reporter: calixte, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash, regression, Whiteboard: qa-not-actionable)
Crash Data
This bug was filed from the Socorro interface and is
report bp-15202dec-4efb-4469-a3b3-01b540180215.
=============================================================
Top 10 frames of crashing thread:
0 libMali.so libMali.so@0x1081c
1 libMali.so libMali.so@0x100456
2 libMali.so libMali.so@0x10045a
3 libMali.so libMali.so@0x10045a
4 libMali.so libMali.so@0x5cd16
5 libMali.so libMali.so@0x5b636
6 dalvik-main space (deleted) dalvik-main space @0xa7c2cf5
7 libxul.so wcsrtombs
8 libEGL.so libEGL.so@0xda0f
9 libxul.so wcsrtombs
=============================================================
There is 1 crash in nightly 60 with buildid 20180213100129. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 785440.
[1] https://hg.mozilla.org/mozilla-central/rev?node=d2dea7eb260f
Flags: needinfo?(mstange)
Reporter | ||
Updated•7 years ago
|
Crash Signature: [@ dalvik-main space (deleted)@0xa7c2cf5] → [@ dalvik-main space (deleted)@0xa7c2cf5]
[@ mozilla::AutoProfilerLabel::AutoProfilerLabel]
Updated•7 years ago
|
Priority: -- → P3
Updated•4 years ago
|
Whiteboard: qa-not-actionable
Updated•2 years ago
|
Severity: critical → S2
Comment 1•2 years ago
|
||
Since the crash volume is low (less than 5 per week), the severity is downgraded to S3
. Feel free to change it back if you think the bug is still critical.
For more information, please visit auto_nag documentation.
Severity: S2 → S3
Comment 2•2 years ago
|
||
It looks like we do still have some crashes in AutoProfilerLabel::AutoProfilerLabel
.
Flags: needinfo?(mstange.moz)
You need to log in
before you can comment on or make changes to this bug.
Description
•