DesugarDexSharding error (Too many open files) when running mobile-install-v3 on large codebase

[snazhmudinov]

We experience an issue when running mobile-install-v3 on a large codebase.

Error log

ERROR: non zero exit: worker spawn failed for DesugarDexSharding
java.lang.IllegalStateException: Desugar failed with exit code: 1
        at com.google.devtools.build.android.DesugarDexShardingAction.desugar(DesugarDexShardingAction.java:166)
        at com.google.devtools.build.android.DesugarDexShardingAction.processRequest(DesugarDexShardingAction.java:391)
        at com.google.devtools.build.android.DesugarDexShardingAction.processRequestForWorker(DesugarDexShardingAction.java:335)
        at com.google.devtools.build.android.DesugarDexShardingAction.lambda$runPersistentWorker$0(DesugarDexShardingAction.java:319)
        at com.google.devtools.build.lib.worker.WorkRequestHandler$WorkRequestCallback.apply(WorkRequestHandler.java:252)
        at com.google.devtools.build.lib.worker.WorkRequestHandler.respondToRequest(WorkRequestHandler.java:480)
        at com.google.devtools.build.lib.worker.WorkRequestHandler.lambda$startResponseThread$1(WorkRequestHandler.java:433)
        at java.base/java.lang.Thread.run(Thread.java:1583)
bazel-out/darwin_arm64-dbg-android-ST-e30d6f35036d/bin/<redacted path>/example.abi.jar
java.io.UncheckedIOException: bazel-out/darwin_arm64-dbg-android-ST-e30d6f35036d/bin/<redacted path>/example.abi.jar
        at com.android.tools.r8.ArchiveClassFileProvider.d(R8_8.9.35_b4dbea2f8bdfdf2cab3ae611558fd558945d3a458bfc50ef035fc9f5ad630d56:22)
        at com.android.tools.r8.ArchiveClassFileProvider.c(R8_8.9.35_b4dbea2f8bdfdf2cab3ae611558fd558945d3a458bfc50ef035fc9f5ad630d56:4)
        at com.android.tools.r8.ArchiveClassFileProvider.<init>(R8_8.9.35_b4dbea2f8bdfdf2cab3ae611558fd558945d3a458bfc50ef035fc9f5ad630d56:27)
        at com.android.tools.r8.ArchiveClassFileProvider.<init>(R8_8.9.35_b4dbea2f8bdfdf2cab3ae611558fd558945d3a458bfc50ef035fc9f5ad630d56:1)
        at com.google.devtools.build.android.r8.Desugar.desugar(Desugar.java:449)
        at com.google.devtools.build.android.r8.Desugar.processRequest(Desugar.java:604)
        at com.google.devtools.build.android.DesugarDexShardingAction.desugar(DesugarDexShardingAction.java:164)
        at com.google.devtools.build.android.DesugarDexShardingAction.processRequest(DesugarDexShardingAction.java:391)
[ted-xie](https://github.com/ted-xie)
ted-xie commented [12 hours ago](https://github.com/bazelbuild/rules_android/issues/449#issuecomment-4239093131)
ted-xie
12 hours ago

Using patched bazel 7.7.1
Using rules_android 0.7.1
OS: Tahoe 26.2

[snazhmudinov]

One way we were able to "fix" it was adding "-XX:-MaxFDLimit" to BASE_JVMOPTS in tools/jdk/jvmopts.bzl.

[ted-xie]

Interesting that you were able to work around it with a JVM option. I guess since the failure in mobile-install occurs within the JVM, that fix works, but the failure in resource packaging (#449) originates from a native binary, the same fix can't be applied there.

I would encourage you to see if there are ways you can split apart your resource deps somehow. We also have huge apps internally with a lot of resources and have not run into this issue before.