Updates:
Status: WorkingAsIntended
Comment #17 on issue 2534 by [email protected]: mega.co.nz large
file transfers: GC never runs due to constant activity
http://code.google.com/p/v8/issues/detail?id=2534
I investigated this issue by uploading a 4.4GB file to mega.co.nz and
observing the memory footprint. The process memory increases to a little
bit below 5GB and doesn't release the memory even after the upload. But the
JavaScript heap size stays at about 30MB throughout this process. So it is
_not_ a GC issue.
Furthermore I looked at whether new Isolates are initialized. It turns out
that roughly 5000 Isolates are initialized and torn down during the upload.
I suspect web workers (just guessing here) cause the initialization of
Isolates because that is the only place in Chrome that spawns additional
Isolates.
Also I wrote a small unit test that spins up about 5000 V8 Isolates from a
stand-alone shell, executes a trivial script in them and tears them down
again. The overall memory consumption after doing this is about 3MB,
roughly the same as performing those steps on just one Isolate. This
suggests it is _not_ a V8 issue.
This could very well be a bug in Chrome or just the site itself is holding
on to part of the web workers.
--
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.
