Ticket #2531080 (closed defect)
ReporterChris Klaiber |
Opened: 09/9/11 Last modified: 06/12/12 Status: closed Type: defect Resolution: duplicate Duplicate of: #2529690 |
Owner Luke Smith |
Target Release: 3.6.0 Priority: P3 (normal) |
|---|---|---|---|
| Summary: | Memory leak from GUID-based caching in Y.before() and Y.after() | ||
| Description: | Y.before() and Y.after() rely on Y._inject() (http://yuilibrary.com/yui/docs/api/files/event-custom_js_event-do.js.html#l117) which caches information using a GUID stamp. When running YUI in NodeJS and passing in an object to stamp that is unique within each request, data is added to the cache and never removed, and a memory leak results. If there are other places with YUI where GUID stamp-based caching is used, they may also leak memory in a similar manner. |
||
| Type: | defect | Observed in Version: | 3.4.0 |
| Component: | Event | Severity: | S3 (normal) |
| Assigned To: | Luke Smith | Target Release: | 3.6.0 |
| Location: | Library Code | Priority: | P3 (normal) |
| Tags: | nodejs, searchdirect | Relates To: | |
| Browsers: | N/A | ||
| URL: | |||
| Test Information: | Using yui3@0.5.34 and yui3-core@3.4.0 on NodeJS 0.4.5, output is: {"rss":26628096,"vsize":3125485568,"heapTotal":18382208,"heapUsed":8969544} - initial Notice how the heapUsed remains high even after the 10 second timeout to allow the GC to run. The sample program: var YUI = require("yui3").YUI, function showMem(msg) { YUI().use("event", function(Y) { Y.before(function() { showMem("after " + iterations + "x Y.before()"); //wait for GC to run |
||
Change History
|
Posted: 09/9/11
|
|
Posted: 09/9/11
|
|
Posted: 09/9/11
|
|
Posted: 09/10/11
|
|
Posted: 09/11/11
|
|
Posted: 11/9/11
Bug scrub. Moving to 3.NEXT with the intention to pull into 3.6.0. 3.5.0 is all DataTable for me, so I can't afford the split bandwidth. |
|
Posted: 04/2/12
|
|
Posted: 04/2/12
|
|
Posted: 04/5/12
|
|
Posted: 05/8/12
|
|
Posted: 06/12/12
|
|
Posted: 06/12/12
This ticket was marked as a duplicate of #2529690 |
|
Posted: 06/12/12
Was fixed in 3.6.0 pr1 |
|
Posted: 06/12/12
|
Dav Glass
Setting this to 3.NEXT, but I will try to pull this into 3.5.0. There are other leaks in the event system that I want to address in that release.