Ticket #2530446 (closed defect)
Reporter Stjepan Rajko |
Opened: 06/18/11 Last modified: 08/18/11 Status: closed Type: defect Resolution: fixed |
Owner  Matt Sweeney |
Target Release: 3.4.0 Priority: P3 (normal) |
|---|---|---|---|
| Summary: | memory leak in Node.replace, when Node.create returns a fragment | ||
| Description: | when given a string argument, Node.replace calls Node.create. If Node.create returns a fragment, Node.replace should destroy the fragment, but it doesn't, so the fragment Node stays in _instances. Please see http://jsfiddle.net/TTNHx/1/ for an example. |
||
| Type: | defect | Observed in Version: | 3.3.0 |
| Component: | Node | Severity: | S3 (normal) |
| Assigned To: | Matt Sweeney | Target Release: | 3.4.0 |
| Location: | Priority: | P3 (normal) | |
| Tags: | memory leak, node, create, replace | Relates To: | |
| Browsers: | N/A | ||
| URL: | http://jsfiddle.net/TTNHx/1/ | ||
| Test Information: | The provided example will leak memory every second, stemming from the calls to replace('<div></div><div></div>'), each of which results in a fragment Node which does not get cleaned up. |
||
Change History
|
Posted: 06/27/11
|
|
Posted: 06/27/11
|
|
Posted: 06/27/11
|
|
Posted: 07/27/11
|
|
Posted: 08/18/11
|
