You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue might be a little, uh, unique. I'm trying to beautify 27MB of JS (output from Unity -> Emscripten -> JS) to debug it. We run out of memory a few minutes into the process.
➜ Release js-beautify Mozilla.js
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
[1] 49429 abort js-beautify Mozilla.js
➜ Release node --max_old_space_size=2000 /Users/Nicholas/.nvm/versions/node/v0.12.0/bin/js-beautify Mozilla.js
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
[1] 49862 abort node --max_old_space_size=2000 Mozilla.js
I can't expand the amount of memory used much further with immediately segfaulting. Not sure how feasible it is, but it might be nice to think about how this project could be re-architected to use multiple processes for large input files.
The text was updated successfully, but these errors were encountered:
This issue might be a little, uh, unique. I'm trying to beautify 27MB of JS (output from Unity -> Emscripten -> JS) to debug it. We run out of memory a few minutes into the process.
I can't expand the amount of memory used much further with immediately segfaulting. Not sure how feasible it is, but it might be nice to think about how this project could be re-architected to use multiple processes for large input files.
The text was updated successfully, but these errors were encountered: