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
I tried to run twiggy paths on my wasm binary but it kept climbing in memory usage until it was using over 10 gigs of memory and my system ran out of memory.
twiggy version: twiggy-opt 0.6.0
🌍 Test Case
GitHub doesn't let me upload wasm files directly so this is a zip with the file inside it. It's a 2.32 megabyte binary compiled using wasm-pack from rink-js.
Have a Windows 10 PC with 16 gigabytes of memory. Other OSes or amounts of RAM might work too.
Run twiggy paths rink_js_bg.wasm.
Wait like 10 minutes.
OOM panic.
😲 Actual Behavior
Something like "Failed to allocate 224 bytes" printed to the console and then all the apps on my PC crashed including the terminal Twiggy was running in.
🤔 Expected Behavior
I want to use Twiggy to figure out why my binary is so big.
The text was updated successfully, but these errors were encountered:
🐛 Bug Description
I tried to run
twiggy paths
on my wasm binary but it kept climbing in memory usage until it was using over 10 gigs of memory and my system ran out of memory.twiggy version: twiggy-opt 0.6.0
🌍 Test Case
GitHub doesn't let me upload wasm files directly so this is a zip with the file inside it. It's a 2.32 megabyte binary compiled using wasm-pack from rink-js.
rink_js_bg.zip
👟 Steps to Reproduce
twiggy paths rink_js_bg.wasm
.😲 Actual Behavior
Something like "Failed to allocate 224 bytes" printed to the console and then all the apps on my PC crashed including the terminal Twiggy was running in.
🤔 Expected Behavior
I want to use Twiggy to figure out why my binary is so big.
The text was updated successfully, but these errors were encountered: