Open
Bug 1245618
Opened 9 years ago
Updated 2 years ago
crash in RelazifyFunctions
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
REOPENED
People
(Reporter: dhessel71, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: crash, Whiteboard: qa-not-actionable)
Crash Data
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:47.0) Gecko/20100101 Firefox/47.0 Build ID: 20160203030249 Steps to reproduce: See crashreport/dump at https://crash-stats.mozilla.com/report/index/11808ec6-947e-410c-acb1-674222160203 Actual results: Crash @ RelazifyFunctions, randomly
Also it seems alot of crashes recently are in RelazifyFunctions, see: https://crash-stats.mozilla.com/report/list?signature=RelazifyFunctions#tab-comments Those comments show that crashes on this adress generally happen on casual browsing/typical internet usage. Myself I cannot recall anymore what scenario it happened with me.
I think this may have caused this crash: http://hg.mozilla.org/mozilla-central/rev/b2a3dc4b161f Offset crash file, revision b2a3dc4b161f listed on crashdump. Anyone can confirm or research further?
Flags: needinfo?(philringnalda)
Comment 4•9 years ago
|
||
That changeset is a merge from mozilla-inbound and fx-team, it has no actual content, and because your "a lot of crashes" are two on the trunk and the rest on release versions going back months, there's no reason to think you'll find the cause in a trunk commit anyway.
Flags: needinfo?(philringnalda)
Reopening bug since there are crash reports in the last 6 months.
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WORKSFORME → ---
Whiteboard: qa-not-actionable
Updated•3 years ago
|
Blocks: sm-defects-crashes
Updated•2 years ago
|
Severity: critical → S2
Comment 6•2 years ago
|
||
Since the crash volume is low (less than 15 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
You need to log in
before you can comment on or make changes to this bug.
Description
•