OOM (GC overhead limit exceeded) on large multi-module projects

[kiwiandroiddev]

Describe the bug
I'm working towards disabling jetifier on a large multi-module Android project. The issue I'm seeing with the plugin is of long execution times and eventual crashing of the task with an out of memory error, e.g.

* What went wrong:
Execution failed for task ':app:canISayByeByeJetifier'.
> GC overhead limit exceeded

Increasing the java heap size helps insofar as the task runs for longer before crashing (sometimes identifying support-lib dependencies before it does so 👍 ). However even with org.gradle.jvmargs=-Xmx32768m the task still crashes after ~30 min of execution.

A workaround I've found is to apply the bye-bye-jetifier plugin to individual feature modules in the project rather than the app module. However this can be quite time-consuming depending on the number of modules.

Is there a change to the scanning algorithm that could be made to make it less memory-intensive for multi-module projects?

P.S. thanks for your work on this plugin, despite this issue I've used it to successfully identify and upgrade a number of libraries still depending on the support lib with the workaround above.

[wyhmoon]

+1

[Undefined-User]

Same problem, it just a time & memory eater and cannot use in most of projects. I tried allocating 400GB memory for Gradle, it ran out memory after few hours but not give any results.