Comment #30 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
and the saga continues...
even with the fix I referenced above (pull request #6856), we (AngularJS)
are still getting reports of leaks.
I was able to reproduce a bunch of them and documented them in this drive
folder:
https://drive.google.com/folderview?id=0B7Ovm8bUYiUDLWM1cTNZeHJSbWs&usp=drive_web
the folder contains subfolders, each containing an application runable from
file://, a heap snapshot and a screenshot of heap profiler showing a leak.
Each snapshot was done for a slightly different app (use diff to see the
differences between snapshotX/app vs snapshotY/app.
Each snapshot contains leak with (slightly) different retainer paths.
snapshots 4 and 5 were taken with 36.0.1919.2 canary
snapshots 1,2,3,5 and 7 were taken with 33.0.1750.152
the good news is that M36 leaks *significantly* less than M33 but even M36
is not perfect as captured by snapshots 4 and 5
--
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/d/optout.
