Comment #21 on issue 2073 by [email protected]: Garbage collector sometimes
fails on objects with Object.defineProperty (memleak?)
http://code.google.com/p/v8/issues/detail?id=2073
I landed a fix for one class of memory leaks in revision 15452
(https://code.google.com/p/v8/source/detail?r=15452). This fix is in Chrome
Canary 30.0.1560.1 (V8 3.20.3).
It fixes two angular js issues:
1) https://github.com/angular/angular.js/issues/1313
2) https://github.com/angular/angular.js/issues/2624
Running the test (http://jsfiddle.net/LEWmd/54/) from the first issue with
AngularJS 1.0.2 causes unbounded memory growth in Chrome Dev, but Chrome
Canary stays at 90MB.
I slightly modified the test from the second issue to be more deterministic
and to always stop with two items:
http://plnkr.co/edit/yRs6MbzphusN2K2hlihI?p=preview
Chrome Canary has 7 Child objects in the heap snapshot, and Chrome Dev has
290 Child objects.
There are still other kinds of memory leaks that are uncovered by
internally reported test:
- maps in monomorphic ICs keep garbage alive.
- constant function pointers in optimized code keep garbage alive.
I'll keep this issue open until those leaks are fixed.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
