:information_source: Unfortunately Kotlin Gradle p...
# gradle
t
ℹ️ Unfortunately Kotlin Gradle plugin 1.5.0 has a memory leak that was noticed too late (should be fixed in 1.5.10), but temporary workaround is available: https://youtrack.jetbrains.com/issue/KT-46368#focus=Comments-27-4868598.0-0
👍 5
d
Is this only an issue in specific cases, or should the fix be applied to all projects using 1.5.0?
t
to all projects, but mostly it is noticeable in multimodule projects
👍🏼 1
d
Any ETA for 1.5.10?
t
around end of May
d
Thanks! I guess we'll have to go for the workaround in the meantime...
p
Workaround seems to add build listener which makes it incompatible with configuration cache? https://docs.gradle.org/7.0/userguide/configuration_cache.html#config_cache:requirements:build_listeners
t
yes, you are right. Initial changes that introduced this leak were addressing configuration cache compatibility
👍 1
n
Is multi module referring to Gradle modules, or Kotlin modules?
z
Published a simple Gradle plugin that auto-patches this leak with the workaround impl until it's fixed in Kotlin 1.5.10. https://github.com/ZacSweers/kgp-150-leak-patcher
👍🏼 1
👍 2
d
Maybe this should be in #feed? Thanks alot! I didn't like adding buildSrc to all our projects just for this temporary patch...