Comment #9 on issue 4121 by [email protected]: Regression: Memory leak
since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121
I had the same issue of the heap snapshots being just a few mb while the
process kept growing in size. Specifically, if you serve html files
compiled by jade of around 12kb, a few thousand requests are enough to send
the process to 500mb. And this number never goes down. It just keeps
climbing until it hits the limit set by max-old-space.
Due to the low heap numbers, I assumed that in "reality" v8 was doing fine,
but actually performance degraded a lot. I would suspect that GC now got
triggered more often than it would at a process size of 20mb.
Also, regarding the idea suggested in #8, that sounds like an improvement
for the mass creation of objects, but why, if you leave the process alone
for a few minutes, has the current GC not cleared the leftovers?
--
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.
