Open slingerbv opened 3 weeks ago
npm run execute -- check https://github.com/joenali/waterfall gives "| parser | ParserBase.js 104 | [ DEBUG ] Parsing ./source/js/bundle_pin_5.js"
Problem seems to be here: Logger.Debug( Parsing ${fileName} , Logger.GetCallerLocation()); const clearCache = idx == batchSize - 1; const hashes = this.ParseSingle(fileName, data, clearCache); Logger.Debug( Finished parsing file ${fileName}. Number of methods found: ${hashes.length} , Logger.GetCallerLocation() );
Probably a type problem?
Probably because process chickens out at 10GB on most computers, although not on Aminul's ;-). Don't know what's wise: why is the parser consuming so much memory? Probably same problem as the large files problem.
npm run execute -- check https://github.com/joenali/waterfall gives "| parser | ParserBase.js 104 | [ DEBUG ] Parsing ./source/js/bundle_pin_5.js"
Problem seems to be here: Logger.Debug( Parsing ${fileName} , Logger.GetCallerLocation()); const clearCache = idx == batchSize - 1; const hashes = this.ParseSingle(fileName, data, clearCache); Logger.Debug( Finished parsing file ${fileName}. Number of methods found: ${hashes.length} , Logger.GetCallerLocation() );
Probably a type problem?