Closed
Bug 1152608
Opened 11 years ago
Closed 11 years ago
On first glance a "not" is missing.
Categories
(Developer Documentation Graveyard :: JavaScript, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: trncfrmcn, Unassigned)
Details
(Whiteboard: [specification][type:bug])
What did you do?
================
1. Turned into Garbage collection (reading, literally).
2. Got into the topic.
3. Found a "not" not there.
What happened?
==============
Limitation : cycles
This naive algorithm has the limitation that if objects reference one another (and form a cycle), they may be "not needed anymore" and yet not garbage collectable.
What should have happened?
==========================
Limitation : cycles
This naive algorithm has the limitation that if objects reference one another (and form a cycle), they may be not "not needed anymore" and yet not garbage collectable.
Is there anything else we should know?
======================================
I need assistance in this, as I said. Maybe I overread something. On first glance it looked like so...https://developer.mozilla.org/en-US/docs/Web/JavaScript/Memory_Management#Limitation_.3A_cycles
And this is the wrong form to report, I guess (had another somewhen), but forgive me for late night not finding it%)P.
Updated•11 years ago
|
Component: General → JavaScript
Product: Mozilla Developer Network → Developer Documentation
Comment 1•11 years ago
|
||
I moved the large comment in the code into the main text as it describes the cycle limitation better. Hope this helps :)
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•