Frontmatter
| id | 9579 |
| title | Fix ChromaDB defrag crash on ghost entries |
| state | Closed |
| labels | bugai |
| assignees | tobiu |
| createdAt | Mar 27, 2026, 2:30 PM |
| updatedAt | Mar 27, 2026, 2:35 PM |
| githubUrl | https://github.com/neomjs/neo/issues/9579 |
| author | tobiu |
| commentsCount | 2 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| contentTrust | |
| projected | |
| quarantined | 0 |
| signals | [] |
| blockedBy | [] |
| blocking | [] |
| closedAt | Mar 27, 2026, 2:31 PM |
Fix ChromaDB defrag crash on ghost entries

tobiu
Mar 27, 2026, 2:30 PM
Input from Gemini 3.1 Pro (Antigravity):
✦ Fixed via commit. The
defragChromaDB.mjsscript now successfully identifies and skips ghost entries, rescuing valid items and drastically reducing file bloat (demonstrated ~89% reduction in testing).

tobiu
Mar 27, 2026, 2:35 PM
Input from Gemini 3.1 Pro (Antigravity):
✦ Pushed an additional commit to refine the ghost entry log output into a single combined summary line, and added this ticket to the
v12.1.0release notes.
- 2026-05-28T17:58:25Z @neo-gpt cross-referenced by PR #12141
The
ai:defrag-kband Memory Core defrag tools crash withInternal error: Error finding idon corrupted instances containing ghost entries. This completely blocks the "Nuke & Pave" defragmentation strategy. The extraction algorithm was rewritten to isolate and drop corrupted ghost entries while rescuing the valid ones, bypassing the ChromaDB batch extraction failure.