Skip to content

after index a java project, ui slow #1189

Open

Description

@LinWanCen

Version

codebase-memory-mcp 0.8.1

Platform

Windows (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

ui

What happened, and what did you expect?

I run mvn clean and delete graphify-out, want delete index before, index new again, can not delete, can not index new

Reproduction

delete and index in ui

Logs


Diagnostics trajectory (memory / performance / leak issues)


Project scale (if relevant)

629319 nodes 1351768 edges 26065 files

Confirmations

  • I searched existing issues and this is not a duplicate.
  • My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.

Activity

  1. added
    stability/performanceServer crashes, OOM, hangs, high CPU/memory
    awaiting-reporterWaiting on the reporter for info/repro; stale bot will warn then close
    on Jul 22, 2026
  2. added this to the 0.9.1-rc milestone on Jul 22, 2026
  3. added
    priority/highNeeds near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.
    on Jul 22, 2026
  4. github-actions commented on Jul 22, 2026

    @github-actions

    Thanks for the report! To move this forward we need a bit more so we can reproduce it ourselves:

    • the codebase-memory-mcp --version you're on
    • the exact steps or command you ran
    • a public repo (or a small dummy snippet) that shows the problem — please don't paste proprietary code

    Once that's here we'll pick it straight back up. Heads-up: issues left awaiting-reporter are automatically closed after a few weeks of silence, but a comment reopens the door anytime.

  5. DeusData commented on Jul 22, 2026

    @DeusData
    Owner

    Thanks for the large-graph report. Because this is on v0.8.1 and the current description combines slow rendering, failed deletion, and failed re-indexing without the exact response or log, we need one focused retest on v0.9.0: the downloaded archive name, the first UI action that fails, the /rpc response or browser console error, and the corresponding server log lines. awaiting-reporter is set until that is available.

  6. github-actions commented on Aug 13, 2026

    @github-actions

    This issue has been waiting on more information for 21 days (a version, exact steps, or a public repro), so it's now marked stale. It will not be closed automatically — a maintainer reviews stale issues by hand. Adding a comment with the details clears the label and puts it straight back in the queue. We're happy to pick it back up the moment we can reproduce it.

  7. added
    staleNo activity after an info request; will be closed soon
    on Aug 13, 2026
  8. DeusData commented on Oct 19, 2026

    @DeusData
    Owner

    Thank you for the large Java graph report. If this still affects you, please share the current version and the first failing UI action with its response or matching server error. That will let us separate rendering slowness from deletion or indexing failure.

  9. removed
    staleNo activity after an info request; will be closed soon
    on Oct 21, 2026
  10. github-actions commented on Nov 12, 2026

    @github-actions

    This issue has been waiting on more information for 21 days (a version, exact steps, or a public repro), so it's now marked stale. It will not be closed automatically — a maintainer reviews stale issues by hand. Adding a comment with the details clears the label and puts it straight back in the queue. We're happy to pick it back up the moment we can reproduce it.

  11. added
    staleNo activity after an info request; will be closed soon
    on Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    awaiting-reporterWaiting on the reporter for info/repro; stale bot will warn then closebugSomething isn't workingpriority/highNeeds near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.stability/performanceServer crashes, OOM, hangs, high CPU/memorystaleNo activity after an info request; will be closed soonux/behaviorDisplay bugs, docs, adoption UXwindowsWindows-specific issues

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions