Skip to content

Conversation

soywiz-invideo
Copy link

io.deepmedia.tools.publisher was the culprit of the huge gradle leak :)

@soywiz-invideo soywiz-invideo changed the base branch from main to dev April 21, 2022 19:02
@sahilbajaj
Copy link

Wow... How did you even find this! 😱

@mayankmkh
Copy link

@soywiz-invideo
Copy link
Author

@sahilbajaj you have to merge it:

Screenshot 2022-04-21 at 21 09 48

@sahilbajaj sahilbajaj merged commit 9525108 into dev Apr 21, 2022
@soywiz-invideo
Copy link
Author

@sahilbajaj

Wow... How did you even find this! 😱

it was not happening in korge-next so not a KMM issue. And just by calling ./gradlew several times caused the leak, so it was at configuration time. It had to be a plugin. I used VisualVM to do ./gradlew GC + headdump a couple of times, then checked the instances that were leaked. And I found an instance in a package from that library. But well I guess that disabling all the plugins one by one would have helped too. Though sometimes disabling them breaks the build

@mayankmkh mayankmkh deleted the soywiz-invideo-patch-1 branch May 4, 2022 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants