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
Apparently, 5af9d82 made the overhead effectively linear, improved the speed to become a few hundreds of milliseconds, and helped the script not crash. However, the generated rewritten_google_crashed_us.js crashes the browser tab when pasted into one.
However, Uncaught RangeError: Maximum call stack size exceeded showed up a few times in my testing, so it is safe to assume this would be the reason.
Increasing the stack size to 4GB seems to allow for a maximum 8 nested evals. Further increasing the stack size causes crashes without visiting any webpages.
Crashed while loading Google Search because of OOM.
I then downloaded the 205k file itself and confirmed that Node was using 3.5GB of memory and then killed itself due to the JS heap OOM.
I increased heap limit to 10GB. It used around 8GB of RAM and eventually threw an error saying the string is too long for
String.replace
:The string length limit in V8 is 512MB, so the rewritten string is clearly too long. We need to find ways to reduce its size.
Also, this process takes over a minute, too slow. Not sure where the bottleneck comes from. Maybe should not have written it in JS.
The text was updated successfully, but these errors were encountered: