Open
Bug 1310932
Opened 8 years ago
Updated 2 years ago
Crash in js::jit::Assembler::bind
Categories
(Core :: JavaScript Engine: JIT, defect, P3)
Tracking
()
REOPENED
Tracking | Status | |
---|---|---|
firefox52 | --- | wontfix |
People
(Reporter: ting, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash, Whiteboard: qa-not-actionable)
Crash Data
This bug was filed from the Socorro interface and is
report bp-8d3136c3-dc7a-40c6-a531-a2b5f2161018.
=============================================================
#2 of Nightly 20161016030205 on Android, 2 crashes from 1 installations. But there are 3463 crash in the last 6 months.
Comment 1•8 years ago
|
||
We are tracking a similar bug which is mostly on MacOS in Bug 1124397.
(In reply to Ting-Yu Chou [:ting] from comment #0)
> 2 crashes from 1 installations.
Unfortunately we are unable to reproduce it so far, if we got contact information from these bug reports, this might be worth asking our users if they can help us investigate this issue with custom builds.
Priority: -- → P3
See Also: → 1124397
Updated•8 years ago
|
Flags: needinfo?(janus926)
Comment 2•8 years ago
|
||
Since these crashes are on Android and therefore ARM, they will *not* be caught by the infrastructure I recently added, since AssemblerBuffer is only used on x86 and x64. Once bug 1309573 is fixed, we will hopefully get some more information for those platforms, but the cause might be different on Android.
Reporter | ||
Comment 3•8 years ago
|
||
You can filter out the reports which came with the reporter's email on Socorro, like: https://crash-stats.mozilla.com/signature/?product=FennecAndroid&email=%21__null__&signature=js%3A%3Ajit%3A%3AAssembler%3A%3Abind&date=%3E%3D2016-10-12T02%3A39%3A00.000Z&date=%3C2016-10-19T02%3A39%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=email&_sort=-date&page=1
Flags: needinfo?(janus926)
Comment 4•8 years ago
|
||
Mass wontfix for bugs affecting firefox 52.
Reopening bug since there are crash reports in the last 6 months.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Whiteboard: qa-not-actionable
Updated•3 years ago
|
Blocks: sm-defects-crashes
Comment 6•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: critical → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•