-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[gui] Launch4j created Jadx-version does not show classes from contained DEX file(s) #949
Comments
@skylot Thanks for fixing this problem. The new unstable version now correctly loads all classes again. While playing around with the new unstable version I noticed something strange: On my Windows system the jadx-gui-dev.exe versions now ignore the configured maximum heap size. No matter what is configured in build.gradle Jadx ends up with 1GB maximum heap (on a system with 16GB RAM installed). Only if I completely disable the heap configuration of Launch4j (results in 3.99GB max heap) or if I create a When I start jadx-gui-dev.exe in debug mode using
It seems like for an unknown reason launch4j thinks that the used JRE is a 32bit one. Looking at the available configuration options I found out that I can avoid this problem by adding the configuration option After some more tests tests I identified commit c62039f as the problem source. |
Signed-off-by: Skylot <skylot@gmail.com>
@jpstotz I found a root cause of the issue: during shadow jar build plugins service files overwrite each other and only one plugin left to load. I fix this by the additional option to shadowJar plugin. |
Looks like all issues fixed here, closing. |
The current builds of Jadx-gui.exe created via
gradlew clean createExe
are defect (tested with the provided unstable exe version https://bintray.com/skylot/jadx/download_file?file_path=jadx-gui-1.1.0-b1301-65553c15.exe as well as self-compiled one).If you use one of this versions it loads APK files fast but the class tree afterwards only contains the generated
R
class.The shown log does not show any errors:
The text was updated successfully, but these errors were encountered: