James Krot

I am getting a lot of that as well, what parsing method are you using. I get a similiar issue with dicomParser.explicitDataSetToJS but not with dicomParser.parseDicom

From what I can remember it was due to some tags just being completely missing not empty that the parser was expecting or chosing the end tag for parsing and...

Fyi good reading on this topic is http://stackoverflow.com/questions/1596782/how-to-unset-a-javascript-variable #4 https://www.toptal.com/javascript/10-most-common-javascript-mistakes https://auth0.com/blog/four-types-of-leaks-in-your-javascript-code-and-how-to-get-rid-of-them/

So I used that as an example of previous stuff, I think what is happening is that a fileReader is getting set for each file and not just one fileReader...

I am still confirming that is the case, I am not sure but I am still seeing some memory issues even with my changes. On Fri, Aug 5, 2016 at...

I have made headway on this https://github.com/chafey/dicomParser/blob/master/src/parseDicomDataSet.js line 36 & 70 declaring the variable in the loop was causing a heap leak for me. I am still poking around because...

Correct the problem is I am maxing out my heap so when that happens the parsing goes to an absolute crawl waiting for the garbage collector to clean up so...

I also played around with https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/delete

So the only way I was able to resolve this was to setup workers and to destroy them when done. I tried forcing the collection to happen in multiple places...

So still working on this, I am now classifying this as a heap management issue. So the library does a ton of string creation everywhere and that is all fine...