Memory leak in build scan plugin?

performance

(Markus Kohler) #1

Hi,
I’m running gradle from HEAD using the daemon mode, with the 1.6 build scan plugin activated, and it looks like there might be a memory leak.
I’ve got 45 instances of org.gradle.launcher.daemon.server.scaninfo.DefaultDaemonScanInfo$2
with each of them retaining around 300Kbyte (a JSON string):

Not sure whether that Hashmap is ever cleaned up, but I’m not sure it is a good idea to retain large JSON strings.

Regards,
Markus


(Etienne Studer) #2

Hi Markus

Thanks for your report. We will look into it and get back to you once we have news.

Kind regards, Etienne


(Luke Daley) #3

Hi @Markus_Kohler,

This is actually just in the build tool, not the scans plugin. What’s confusing is that it’s something in the build tool for the scans plugin.

Would you mind raising this at https://github.com/gradle/gradle/issues ?


(Markus Kohler) #4

Done:


(Felipe Fernández) #5

This leak has been fixed with this PR: https://github.com/gradle/gradle/pull/1736

Thanks again for reporting it @Markus_Kohler.