Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Twiggy used too much memory and OOM panicked #500

Open
tiffany352 opened this issue Sep 20, 2020 · 0 comments
Open

Twiggy used too much memory and OOM panicked #500

tiffany352 opened this issue Sep 20, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@tiffany352
Copy link

🐛 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

  1. Have a Windows 10 PC with 16 gigabytes of memory. Other OSes or amounts of RAM might work too.
  2. Run twiggy paths rink_js_bg.wasm.
  3. Wait like 10 minutes.
  4. 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.

@AlexEne AlexEne added the bug Something isn't working label Aug 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants