Closed
Bug 602489
Opened 14 years ago
Closed 6 years ago
Missing write barrier detector needed for NDEBUG
Categories
(Tamarin Graveyard :: Garbage Collection (mmGC), defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: treilly, Assigned: treilly)
References
Details
Attachments
(1 file)
1.12 KB,
patch
|
lhansen
:
review+
|
Details | Diff | Splinter Review |
Just burned 3 days tracking down a Release only missing write barrier. Will be good to have this for shoring up the exact tracing work too. Really this should be called "find marked to unmarked pointers". Which would then have to manually be broken into the missing write barrier and false positive categories. We may even want to add an API to tell the GC a field of a certain object isn't a pointer to enable silencing of false positives.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → treilly
Assignee | ||
Updated•14 years ago
|
Target Milestone: --- → flash10.x - Serrano
Updated•14 years ago
|
Priority: -- → P3
Updated•14 years ago
|
Flags: flashplayer-bug-
Updated•13 years ago
|
Priority: P3 → P4
Assignee | ||
Comment 2•13 years ago
|
||
Bug 604733 is a safety net for exact tracing. If we exactly trace all heap objects (ie no manual tracers or conservative default tracing) and use GCMember and friends everywhere (ie no manual write barriers) then the exact tracing safety net becomes a missing write barrier detector. That's nice.
Updated•13 years ago
|
Priority: P4 → P3
Target Milestone: Q3 11 - Serrano → Q4 11 - Anza
Assignee | ||
Comment 3•13 years ago
|
||
Attachment #535373 -
Flags: review?(lhansen)
Updated•13 years ago
|
Attachment #535373 -
Flags: review?(lhansen) → review+
Any reason to not land the initial patch?
Flags: flashplayer-qrb+
Target Milestone: Q4 11 - Anza → Q1 12 - Brannan
Assignee | ||
Comment 5•13 years ago
|
||
Patch landed: http://hg.mozilla.org/tamarin-redux/rev/60b09e75b375
Target Milestone: Q1 12 - Brannan → Future
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•