UI binary crashes (clean exit) while rendering 3D graph

[sandeepshekhawat]

Bug Report

Description

The ui variant binary crashes with a clean exit (no error message, no stack trace)
while the 3D graph is rendering in the browser. The process simply terminates silently.

Environment

• Version: 0.7.0
• OS: macOS 26.2 (Build 25C56)
• Arch: darwin arm64
• RAM: 16 GB
• Variant: ui (installed via install.sh --ui)

Steps to Reproduce

1. Install the UI variant: curl -fsSL .../install.sh | bash -s -- --ui
2. Run: tail -f /dev/null | codebase-memory-mcp (to keep stdin open)
3. Open http://localhost:9749
4. Wait for 3D graph to render

Observed Behavior

Process exits cleanly mid-render. Logs only show:
level=info msg=mem.init budget_mb=8192 total_ram_mb=16384

No crash dump, no error, no signal info.

Expected Behavior

Graph renders without crashing the process.

Additional Notes

• The MCP stdio tools (search_graph, trace_path, etc.) work fine
• Crash is reproducible every time the graph attempts to render
• KeepAlive in LaunchAgent does not restart the process after this crash

[DeusData]

Thanks for the report. A clean exit (no signal, no stack) mid-render points to a deliberate exit path rather than a SIGSEGV — the UI server runs alongside the MCP stdio loop, so the whole process goes down if either side exits. I can't reproduce it without a bit more:

1. Exit code — capture it right after it dies (e.g. …; echo "exit=$?").
2. Verbose stderr up to the exit — paste the last ~30 lines (the only line so far is mem.init).
3. Graph size — the nodes/edges from the index_repository response for the project you're viewing (you're on 16 GB / budget 8192 MB, so I want to rule out a size/budget exit).
4. Does it reproduce with a small project (a few files), or only on a large graph?
5. After the exit, do the MCP stdio tools still respond, or is the whole process gone?

A repro project (or just its approximate node/edge count) would help most.