search

j4k0xb / webcrack

Deobfuscate obfuscator.io, unminify and unpack bundled javascript
https://webcrack.netlify.app
MIT License
647 stars 73 forks source link

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory #96

Closed muzammil0011 closed 2 weeks ago

muzammil0011 commented 2 weeks ago

Describe the bug

This issue is faced I am working with larger files:

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Expected Behaviour

The code should be decompiled async

Code

/* Its a large file, about 18MB */

Logs

<--- Last few GCs --->

[4472:0000022CD55D72C0]    58560 ms: Scavenge (reduce) 2039.6 (2081.1) -> 2039.4 (2081.6) MB, 10.65 / 0.00 ms  (average mu = 0.167, current mu = 0.003) allocation failure;
[4472:0000022CD55D72C0]    61140 ms: Mark-Compact (reduce) 2040.1 (2081.6) -> 2039.7 (2081.9) MB, 2574.46 / 0.00 ms  (average mu = 0.117, current mu = 0.050) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 00007FF76CB3C94B node::SetCppgcReference+17979
 2: 00007FF76CAA6764 DSA_meth_get_flags+89316
 3: 00007FF76D5249A1 v8::Isolate::ReportExternalAllocationLimitReached+65
 4: 00007FF76D50E0F8 v8::Function::Experimental_IsNopFunction+1336
 5: 00007FF76D36FBA0 v8::Platform::SystemClockTimeMillis+659328
 6: 00007FF76D37BE23 v8::Platform::SystemClockTimeMillis+709123
 7: 00007FF76D379784 v8::Platform::SystemClockTimeMillis+699236
 8: 00007FF76D36C8C0 v8::Platform::SystemClockTimeMillis+646304
 9: 00007FF76D381F3A v8::Platform::SystemClockTimeMillis+733978
10: 00007FF76D3827B7 v8::Platform::SystemClockTimeMillis+736151
11: 00007FF76D3910AF v8::Platform::SystemClockTimeMillis+795791
12: 00007FF76D051DD5 v8::CodeEvent::GetFunctionName+116773
13: 00007FF70D59AAFA
0xdevalias commented 2 weeks ago

@muzammil0011 I suspect that being able to provide the file causing the issue would assist in reproducing and debugging the specifics of the issue, and if there is a viable workaround/bugfix for it.

It would also probably be useful to know the stats of the machine you're running this on, how much RAM it has, whether you're running the browser version or locally, etc. Currently there aren't really a lot of details in your issue that make it particularly actionable (IMO).

j4k0xb commented 2 weeks ago

Try increasing the memory limits: https://webcrack.netlify.app/docs/guide/common-errors.html#heap-out-of-memory