Comment #16 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
Further testing reveals that the XMLHttpRequests allocate memory on a
per-URL basis. Repeatedly sending large requests to the same URL does not
leak beyond the initial allocation.
Solution/ugly hack: Move the path component of the target URL to a custom
header and only use the host part in the XMLHttpRequest.open() call. This
strategy will still waste significant memory with a large number of active
peers, but for now keeps the problem at bay. This will be deployed on
mega.co.nz over the next few hours and should eliminate all crashes related
to large file uploads (especially under Linux, where the tab already
crashes at around 350 MB rather than 1.2-1.5 GB).
As this is probably not a V8 issue, it should be moved to a more
appropriate forum for further investigation and fixing.
--
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.
