Closed Bug 1252651 Opened 8 years ago Closed 7 years ago

Intermittent test_aboutmemory5.xul | application crashed [@ js::detail::HashTable<js::HashMapEntry<char const *,JS::ClassInfo>,js::HashMap<char const *,JS::ClassInfo,js::CStringHashPolicy,js::SystemAllocPolicy>::MapHashPolicy,js::SystemAllocPolicy>::looku

Categories

(Core :: JavaScript: GC, defect, P3)

Product:
Core
Component:
JavaScript: GC
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: KWierso, Unassigned)

Details

(Keywords: intermittent-failure) 

This has spiked significantly over the last few days. Any ideas what might have landed around the 1st to cause this, Terrence?
Component: about:memory → JavaScript: GC
Flags: needinfo?(terrence)
Product: Toolkit → Core
(In reply to Ryan VanderMeulen [:RyanVM] from comment #1)
> This has spiked significantly over the last few days. Any ideas what might
> have landed around the 1st to cause this, Terrence?

I think the only major GC work that landed around then was Emanuel's Arena refactor. That said, this is a UAF in jemalloc memory held via the GC heap. This is super, super weird as we would have poisoned the GC thing too if it had been dead, making the jemalloc memory unreachable. So we have a live GC thing pointing to a malloc allocation that has been freed. Or we're traversing garbage that hasn't been poisoned somehow? I highly doubt the Arena refactor is involved and we're probably not going to be able to do anything here unless we can get it under rr.
Flags: needinfo?(terrence)
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.