Skip to content

Prevent Gradle heap exhaustion between release APK builds - #15

Merged
wizdom13 merged 1 commit into
mainfrom
release-build-memory
Sep 30, 2026
Merged

wizdom13 merged 1 commit into
mainfrom
release-build-memory

Conversation

@wizdom13

@wizdom13 wizdom13 commented Sep 30, 2026 •

Copy link
Copy Markdown
Owner
  • Fix Java heap space in :app:mergeReleaseNativeDebugMetadata from https://github.com/wizdom13/WizeFiles-Pro/actions/runs/36770809071/job/110076408373. The universal APK built successfully; the second (ARM64) build failed in the reused Gradle JVM before signing began.
  • Run each of the three APK builds in a fresh single-use Gradle process with a 6 GiB heap and at most two workers. Reuse compiled outputs on disk between architectures.
  • Keep the app code, native-symbol generation, APK validation and signing steps unchanged; both production releases and PR packaging use this shared script.
  • Validation: shell syntax and whitespace checks pass. The packaging regression tests passed in CI, but both PR workflows were cancelled before completion. The packaging run was cancelled during the native build, before APK assembly/signing/upload; full validation remains pending a fresh release or packaging run. The fix is merged on main at 51c587946a7f82818edad8d42d8d81ad5d2b16f0.

@wizdom13
wizdom13 merged commit 51c5879 into main Sep 30, 2026
2 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant