Closed Bug 598422 Opened 14 years ago Closed 14 years ago

GCAutoEnter::SetGCToNull needs attention

Categories

(Tamarin Graveyard :: Garbage Collection (mmGC), defect, P1)

Product:
Tamarin Graveyard
Component:
Garbage Collection (mmGC)
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WONTFIX
Milestone:
flash10.2.x-Spicy

People

(Reporter: stejohns, Assigned: treilly)

Details

This is needed for some Android builds, but has not landed in avmplus.
See bug 590112, comment 3

The reason I noted there that this is not the right long-term solution is because Tommy thinks we need to investigate why the Android team was doing this in the first place.  It may have been a work-around for a bug in their code, but not a real fix.  We don't know yet.
According to Samuli and Brent, the genesis of this was: "Ultimately, the memory manager is not designed to handle destruction of the GC while it's entered multiple times on the stack.  Modifying the code to handle this would be a large design change, and I'm not sure it's something we really want to support anyway. Samuli has a band-aid fix for this that handles this special case by forcing the stackEnter gc to NULL and long jumping to before the original stack enter.  This seems like a feasible workaround for this edge case."
Hurmph, I hate it when we have a fix and don't have a complete understanding of the problem, I'll try to remedy that.
Assignee: nobody → treilly
Status: NEW → ASSIGNED
Flags: flashplayer-qrb+
Priority: -- → P2
Target Milestone: --- → flash10.2.x-Spicy
Priority: P2 → P1
The need for this hasn't been adequately demonstrated despite repeated attempts at explaining why it shouldn't be necessary and asking for more information.    Resolving as wont fix.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
bulk verifying resolved !fixed issues
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.