Updates:
Owner: ish...@chromium.org
Labels: -Area-Compiler Area-GC
Comment #3 on issue 4121 by jkumme...@chromium.org: Regression: Memory leak
since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121
Run the example with --trace-gc and observe more retained memory after
every mark-compact cycle; when I bump up the iteration count to 5M I see up
to ~300MB. However, the test case doesn't create any long-lived objects, so
memory consumption shouldn't grow over time.
Further observations:
(1) --trace-gc-verbose says the memory is in old space.
(2) --trace-gc-object-stats --noincremental-marking doesn't list any type
of object that would account for such memory consumption; all the instance
kinds it reports add up to ~1MB.
(3) --noconcurrent-sweeping doesn't change anything.
(4) --stress-compaction seems to fix it; live memory after GC stays
constant at 1.4MB then.
Assigning to memory sheriff for further investigation.
--
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
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
