Closed Bug 1414338 Opened 2 years ago Closed 10 months ago
Crash in Trace
This bug was filed from the Socorro interface and is report bp-ef88babf-4a3b-4023-b637-afc901171028. ============================================================= Low volume crash; 40 crashes in the last week.
Jon, is this actionable?
Reports over the last week: > Firefox 58.0a1: 16 > Firefox 57.0b*: 6 > Firefox 56.0.*: 29 > Firefox ESR 52.4.*: 1 Reports over the last month: > Firefox 58.0a1: 19 > Firefox 57.0b*: 30 > Firefox 56.0.*: 92 > Firefox ESR 52.4.*: 6 At these volumes I don't think this will be fixed for Firefox 56/57.
(In reply to Jason Orendorff [:jorendorff] from comment #1) There's nothing obviously wrong with this code so this is not actionable without STR. CC'ing Jan because it's JIT related.
Having said that, we could add some assertions here.
Attachment #8926858 - Flags: review?(sphink)
Attachment #8926858 - Flags: review?(sphink) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/3b3fdb4f8f36 Add some assertions to TraceDataRelocations r=sfink
This call to TraceDataRelocations() doesn't seem to be hit at all in our tests: https://searchfox.org/mozilla-central/source/js/src/jit/x86-shared/Assembler-x86-shared.cpp#94 But then again that path doesn't appear in any of the crash stacks either.
The leave-open keyword is there and there is no activity for 6 months. :jonco, maybe it's time to close this bug?
This is another ongoing crash during marking. It's still happening but is not actionable as such. Marking as stalled.
Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → WORKSFORME
10 months ago
You need to log in before you can comment on or make changes to this bug.