Is it possible to clean memory after FileReader?

Bug has been marked as INVALID, since it turned out that I wasn't in fact re-using FileReader object properly.

Bug has been marked as INVALID, since it turned out that I wasn't in fact re-using FileReader object properly. Here is a pattern, which doesn't hog memory and cpu: function sliceMe() { var file = document. GetElementById('file').

Files0, fr = new FileReader, chunkSize = 2097152, chunks = Math. Ceil(file. Size / chunkSize), chunk = 0; function loadNext() { var start, end, blobSlice = File.prototype.

MozSlice || File.prototype. WebkitSlice; start = chunk * chunkSize; end = start + chunkSize >= file. Size?File.

Size : start + chunkSize; fr. Onload = function() { if (++chunk ReadAsBinaryString(blobSlice. Call(file, start, end)); } loadNext(); } Another bug report has been filed: https://bugzilla.mozilla.

Org/show_bug. Cgi? Id=681479, which is related, but not the evil in this case.

Thanks to Kyle Huey for bringing this to my attention :).

Looks like I got stuck with sendAsBinary now though... life doesn't get easy... – jayarjo Aug 25 at 11:53.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.