- From: Ajaay <notifications@github.com>
- Date: Thu, 09 May 2019 03:05:34 -0700
- To: w3c/FileAPI <FileAPI@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 9 May 2019 10:05:59 UTC
I do think this warrants an answer or at least some direction. In our experience garbage collection does not remove blobs, and therefore the creation of a large number of blobs over time causes the memory used by Chrome to increase until it crashes. The only way we found of getting around that was to use the close method in an electron app where we could enable experimental features without the user needing to do it on their standalone Chrome build. We're now in a position where we cannot upgrade our Electron app because we lose the close method, which renders our app useless. It's a reasonable question to ask what the proper method is of controlling memory use when creating large numbers of blobs on even reasonably specced machines. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/FileAPI/pull/68#issuecomment-490841939
Received on Thursday, 9 May 2019 10:05:59 UTC