-
Notifications
You must be signed in to change notification settings - Fork 11
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
Anyway to reduce the memory use? #6
Comments
I think there are many tools focused on this, or just use builtin pprof. |
Hm, I read OP's message in a different way. Running @joway can you confirm that? |
Oh, I understand what you means now. |
One reason I can imagine is that the decompile creates too many go routine in a split second, consuming all the available memory, but I don't think it's likely to squeeze a machine with 180g of RAM. |
A configurable gc parameter was added in 1.0.5 |
For some binary with large size(like 400MB), it will OOM killed by os. My host have 180GB Memory....
The text was updated successfully, but these errors were encountered: