Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KSP 1.9.21-1.0.15 leaking memory & causing OOMs for Buck #1656

Closed
jbarr21 opened this issue Dec 14, 2023 · 1 comment
Closed

KSP 1.9.21-1.0.15 leaking memory & causing OOMs for Buck #1656

jbarr21 opened this issue Dec 14, 2023 · 1 comment

Comments

@jbarr21
Copy link

jbarr21 commented Dec 14, 2023

KSP 1.9.21-1.0.15 has started leaking memory and causing OOM issues & GC thrash when being used in a daemon environment. Our Buck builds use a long-lived buckd daemon process:

For subsequent commands, Buck checks for the running daemon process and if found, uses the daemon to execute the command. Using the Buck daemon can save significant time as it avoids the overhead of starting a Java virtual machine (JVM) and loading the Buck class files

I performed the same build of a smaller app (larger apps fail to compile after 2x their normal time due to OOM or stuck in GC thrash):

  • 1.0.14: 1.5 GB used
  • 1.0.16: 5 GB used

1.0.16 is on the left, 1.0.14 on the right. At the end of compilation, there were 116 mockproject instances in memory on the new version as opposed to 0 on the older version.
Screenshot 2023-12-14 at 3 06 04 PM

MockProject was identified as a potential leak by Memory Analyzer Tool & the path to GC roots looks like:
Screenshot 2023-12-14 at 3 04 56 PM

@jbarr21
Copy link
Author

jbarr21 commented Jan 9, 2024

dupe since original issue was not fully resolved with the initial fix

@jbarr21 jbarr21 closed this as completed Jan 9, 2024
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

No branches or pull requests

1 participant