Skip to content

JDTLS spawns separate process per subproject in Gradle monorepos #14191

Closed

Description

@ChrisJamesHassell

In Gradle monorepos, JDTLS resolves its root to the nearest build.gradle (subproject level) instead of the workspace root (settings.gradle). This causes a separate JDTLS process (~1-3GB each) per subproject.

Additionally, JDTLS creates temp data directories via fs.mkdtemp that are never cleaned up on shutdown, leaking across sessions.

Activity

  1. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    perfIndicates a performance issue or need for optimization
    on Feb 18, 2026
  2. github-actions commented on Feb 18, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    These issues should be consolidated to avoid duplicate work on the same root cause.

  3. ChrisJamesHassell commented on Mar 5, 2026

    @ChrisJamesHassell
    Author
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

coreAnything pertaining to core functionality of the application (opencode server stuff)perfIndicates a performance issue or need for optimization

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions