There was a report about a potential memory leak: https://github.com/runningcode/gradle-doctor/issues/247
It turned out that this is expected and the plugin stores a quite detailed information about build operations to make needed calculation.
The thing is that memory consumption increases so big that it makes using of the plugin problematic on big projects.
In my environment this is the top-1 memory consumer.
Therefore, I'd like to revive this topic to clarify potential improvements, if possible.
Would it be possible to store this information only for checks that consume it?
Are there any ideas to reduce the amount of data or calculate and discard on the fly?
Hi!
There was a report about a potential memory leak: https://github.com/runningcode/gradle-doctor/issues/247 It turned out that this is expected and the plugin stores a quite detailed information about build operations to make needed calculation.
The thing is that memory consumption increases so big that it makes using of the plugin problematic on big projects. In my environment this is the top-1 memory consumer.
Therefore, I'd like to revive this topic to clarify potential improvements, if possible.
With plugin:
Without plugin: