-
Notifications
You must be signed in to change notification settings - Fork 377
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
There is insufficient memory for the Java Runtime Environment to continue. #37
Comments
Forgot the attachment. |
Using -Xmx5G on the command line helped but it froze my computer for a long time. Don't know that 5G was needed, just what I tried the first time. |
What is the command you run? Any sample we can reproduce on? |
This is the command that worked
Without I can share the aab file if you give me an email to share it with, don't want to upload it here. |
How big is the Bundle and how big is the APK Set? As a short-term workaround, you could possibly try reducing the parallelism using |
aab file is 29 megs. Where do I use |
Sorry, |
Same issue with It happens pretty quickly when trying it with that aab. |
I recommend to build only the APKs for the device you want to test it on. You can do so by passing a device spec to the command (through the --device-spec flag). The device spec file can be generated manually or bundletool also provides a command (get-device-spec) to extract the spec from a connected device. See this documentation. |
Describe the bug
A clear and concise description of what the bug is.
Bundletool version(s) affected
Version: [e.g. 0.3.3] 0.7.1
Stacktrace
To Reproduce
Seems to happen sometimes when running bundletool to generate the signed apks.
Expected behavior
Create the signed apks without the crash.
Environment:
OS: [e.g. iOS 10.3.3]
Ubuntu 18.10
I can attach the hs file it generated but I edited it to remove private parts of my command line.
The text was updated successfully, but these errors were encountered: