I am porting my app from 6.2.3 by creating a new p...
# questionsm
matt.aguirre
11/07/2025, 6:57 PMI am porting my app from 6.2.3 by creating a new project and copying over files so that I can pinpoint dependency issues. I've gotten pretty far (much better than the I've done before), but now I am copying over my controller files and gradlew has started throwing OOM issues. Is this common for anyone else? I can fit about 15 controllers and then it's just OOM. My system has 64 gigs and I've upped the -Xmx to 24g, but nothing is working. I've removed parallel build and set it to --no-daemon, but from what I can see when watching it it never uses more than about 1.6% of my system memory. Any ideas?
matt.aguirre
11/07/2025, 7:05 PMPorting from 6.2.3 to 7.0.1
matt.aguirre
11/07/2025, 7:07 PMSome things I've tried:
1. export GRADLE_OPTS="-Xmx24g -Xms24g"
2. Setting gradle.properties: org.gradle.jvmargs=-Xms1g -Xmx24g -XX:MaxMetaspaceSize=1g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=. -Dfile.encoding=UTF-8 -Duser.timezone=UTC
3. In IntelliJ; setting the JVM Options: -Xmx24g -Duser.timezone=UTC
matt.aguirre
11/07/2025, 7:10 PMAlthough I am pretty sure #3 is for just when it's running, not building
matt.aguirre
11/10/2025, 3:58 PMI don't know why, but a reboot fixed it.
matt.aguirre
11/10/2025, 10:04 PMIt was with my assets, once I changed some of my options in my build.gradle it stopped the OOM issue.
🙏 1
2 Views