Open
Bug 2080740
Opened 1 month ago
Updated 1 month ago
WeakRef behaviour may be inconsistent with the spec after nuking CCW target
Categories
(Core :: JavaScript: GC, defect, P5)
Core
JavaScript: GC
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr153 | --- | wontfix |
| firefox158 | --- | wontfix |
| firefox159 | --- | wontfix |
| firefox160 | --- | fix-optional |
People
(Reporter: jonco, Unassigned)
References
(Regression)
Details
(Keywords: regression)
In the comments of bug 2066622 we decided that the way we handle nuking of CCW WeakRef targets may be not consistent with the spec, since we return undefined even when the original (now nuked) target is still live.
Fixing this could be difficult given our implementation. I don't think this is going to be a big problem however.
| Reporter | ||
Updated•1 month ago
|
Keywords: regression
Regressed by: 2031152
Comment 1•1 month ago
|
||
Set release status flags based on info from the regressing bug 2031152
status-firefox158:
--- → affected
status-firefox159:
--- → affected
status-firefox160:
--- → affected
status-firefox-esr153:
--- → affected
Updated•1 month ago
|
Updated•1 month ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•