This message was deleted.
# generals
Slackbot
06/01/2021, 2:01 AMThis message was deleted.
e
Eli Graber
06/02/2021, 3:37 AMIn the last screenshot the 7.3gb process is gradle daemon, and the 5gb process is the kotlin compiler daemon.
The other screenshots are showing info from jconsole for the gradle daemon. Perhaps there's a classloader leak somewhere? Looks like something is consuming ~100mb of non heap memory every build (the heap usage seems fine), which matches up with watching the gradle daemon process resources go up ~150mb each build.
Eli Graber
06/02/2021, 11:34 PMThis classloader is holding 17.5k classes. There are several others holding ~10k classes.
Eli Graber
06/02/2021, 11:34 PMThese are the gc roots that lead to it
Eli Graber
06/03/2021, 5:07 PMThe 4 next biggest (11k, 10.5k, 10k, and 6k) all essentially look like this:
Eli Graber
06/03/2021, 5:07 PMAnd their gc roots:
Eli Graber
06/03/2021, 11:54 PMUsing the Android hprof analyzer stripped out the data I was trying to look at, so that didn't work.
Looking through the dump, it seems that there's a bunch of these classloaders and the one thing they all have in common is a gc root path through either a `org.jetbrains.kotlin.daemon.common.LoopbackNetworkInterface$ClientLoopbackSocketFactory`or
org.jetbrains.kotlin.daemon.common.LoopbackNetworkInterface$ServerLoopbackSocketFactory