Closed Bug 752387 Opened 13 years ago Closed 13 years ago

Very frequent GC-related crashes with IGC enabled

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philikon, Unassigned)

References

Details

(Keywords: crash, Whiteboard: [js:waitingforinfo][js:dm])

Crash Data

You might want to disable IGC until this is fixed.
(In reply to Gregor Wagner [:gwagner] from comment #1) > You might want to disable IGC until this is fixed. Thanks for the tip. Indeed I had that enabled since I wanted to dogfood it. Guess that worked ;). Disabled it for now. Let me know if you want me to try it again, or run some tests or something.
Severity: normal → critical
Crash Signature: [@ XPCWrappedNative::FlatJSObjectFinalized] [@ @0x0 | nsGenericElement::SaveSubtreeState] [@ nsTHashtable<gfxFont::CacheHashEntry>::s_ClearEntry] [@ js::GCMarker::drainMarkStack] [@ js::gc::MarkKind] [@ CopyUnicodeTo] [@ objc_msgSend | CFEqual]
Keywords: crash
Blocks: 735099
Summary: Very frequent GC-related crashes → Very frequent GC-related crashes with IGC enabled
Whiteboard: [js:p2:fx15][js:dm]
philikon, you should try enabling incremental again and report back if it is okay now. For me at least it is working fine, after a few fixes landed.
Whiteboard: [js:p2:fx15][js:dm] → [js:waitingforinfo][js:dm]
I'm going to assume that this was fixed by whatever other patch that was. Please reopen if you are still having problems, philikon. Thanks!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.