ChromeTraceBuildListener leaking memory?
Created by: msridhar
We did a Buck build with many targets that starting running out of memory, and a heap dump showed ChromeTraceBuildListener
holding on to more than 1.5GB of memory. Looking closer, it seemed that its outputExecutor
had accumulated a huge number of tasks in its queue that were holding on to memory. Running the build with --config log.chrome_trace_generation=false
fixed the issue. It seems there may be a leak here that should be fixed.