Skip to content

Reduce OOM risks with --persistent_android_resource_processor by limiting the number of default workers #8586

@jin

Description

@jin

On a 12-thread machine, building https://github.com/google/google-authenticator-android with --persistent_android_resource_processor and aapt2 spawns 23 JVM workers:

$ ps -ef | grep java.*ResourceProcessorBusyBox.*persistent_worker | wc -l
23

We should cap the number of workers for the resource processor to reduce OOM risks, especially for large builds.

Metadata

Metadata

Assignees

Labels

P1I'll work on this now. (Assignee required)team-AndroidIssues for Android team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions