Comment #13 on issue 4121 by andreasl...@gmail.com: Regression: Memory leak
since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121
oh :( I was about to test it on my local machine
--
You received this message because this project is configured to send all
issue
Comment #11 on issue 4121 by bugdro...@chromium.org: Regression: Memory
leak since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121#c11
The following revision refers to this bug:
https://chromium.googlesource.com/v8/v8.git/+/4cc4bc591cc8ffe7d458f4e89e1fbe3944d44c9f
Comment #12 on issue 4121 by ish...@chromium.org: Regression: Memory leak
since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121
The fix in #11 actually belongs to issue 4173.
--
You received this message because this project is configured to send all
issue
Comment #10 on issue 4121 by andreasl...@gmail.com: Regression: Memory leak
since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121
Just wanted to check in what the status is and if there is anything else I
could do to help you guys fix this.
--
You received this
Updates:
Cc: u...@chromium.org joc...@chromium.org
Comment #5 on issue 4121 by ish...@chromium.org: Regression: Memory leak
since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121
(No comment was entered for this change.)
--
You received this message because this
Comment #7 on issue 4121 by ish...@chromium.org: Regression: Memory leak
since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121
It is interesting that I never saw heap snapshots bigger than 8Mb, while
the Chrome task manager shows memory usage up to 1Gb.
--
You
Comment #6 on issue 4121 by hpa...@chromium.org: Regression: Memory leak
since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121
Stress compaction just forces many gcs and performs a lot of memory
compaction. A bit strange that this option gets rid of the memory. More GCs
Updates:
Status: Assigned
Cc: mvstan...@chromium.org
Comment #8 on issue 4121 by ish...@chromium.org: Regression: Memory leak
since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121
That's an allocation site pretenuring mechanism that causes this.
Currently
Comment #9 on issue 4121 by andreasl...@gmail.com: 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
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
Comment #4 on issue 4121 by andreasl...@gmail.com: Regression: Memory leak
since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121
Yes, I can confirm that the simple for loop example does eventually get
collected.
However, it was just a simple example to show that on
Updates:
Status: Available
Cc: dslo...@chromium.org hpa...@chromium.org
Labels: Type-Bug Priority-Medium Area-Compiler
Comment #2 on issue 4121 by habl...@chromium.org: Regression: Memory leak
since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121
Comment #1 on issue 4121 by andreasl...@gmail.com: Regression: Memory leak
since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121
I have started running
for(var i = 0; i 50; i++) {
(function() {
var array = [{a: 1, b: 'r'}];
13 matches
Mail list logo
