Fix potential file handle leaks by clearing IntelliJ VFS cache#2790
Merged
Conversation
ting-yuan
approved these changes
Feb 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Improves resource management in the KSP Analysis API implementation by ensuring IntelliJ file handlers are properly cleaned up. When using the Kotlin Analysis API, the underlying CoreJarFileSystem maintains a cache of file handlers. If not explicitly cleared, this leads to issues in Windows where the OS holds the lock on a specific file making it impossible to re-run the build unless the existing gradle daemon is terminated. Linux and Mac os are more lenient in terms of file locking so this does not seem to be an issue there
Fixes: #2774