-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Some APK never decompiled, jadx consumes GBs of memory #354
Comments
Yes, with large projects I'm also having the same problem. But running it 2nd time on same folder didn't solve the problem. |
@sergey-wowwow using your apk I can't reproduce this issue. Is problem solved? Can I close it? |
@skylot |
My memory is 8G, I decompile some large APK will be stuck |
The Facebook Messenger app (like all the Facebook apps) is quite large (>100k classes) furthermore the decompilation is limited to one thread (hard coded in code because of "freezes sometime with several threads" according to code comment). Decompilation of large apps with only one thread can be very time consuming. Furthermore I noticed a bug that Jadx hides the progress bar even if the decompilation is still ongoing. |
🎉 This issue has been resolved in version 0.9.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Hi, I've noticed that some APKs are never decompiled, but consumer 16 GBs of memory (I don't have more, so I finished it), but when I run decompilation again, it finishes successfully.
Example of such APK: https://drive.google.com/file/d/16wImr7l426R30u4X2UznHmqJrOCL5U8w/view?usp=sharing
Output of
jstack
:@skylot can you please look at it? I believe it's an issue, but not just big APK
The text was updated successfully, but these errors were encountered: