Frontmatter
| id | 9715 |
| title | Disable Memory Core Hybrid Engine Temporarily |
| state | Closed |
| labels | bugai |
| assignees | tobiu |
| createdAt | Apr 5, 2026, 10:28 AM |
| updatedAt | Apr 5, 2026, 10:30 AM |
| githubUrl | https://github.com/neomjs/neo/issues/9715 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Apr 5, 2026, 10:30 AM |
Disable Memory Core Hybrid Engine Temporarily
Closedbugai
tobiu assigned to @tobiu on Apr 5, 2026, 10:29 AM
tobiu
Apr 5, 2026, 10:29 AM
Switched back to engine: chroma inside memory-core/config.mjs to prevent sequential unit tests from auto-spawning zombie ollama serve processes and maxing out the CPU. Stabilized the build for now.
tobiu closed this issue on Apr 5, 2026, 10:30 AM
The
engine: 'both'hybrid configuration inmemory-core/config.mjswas inadvertently triggeringollama serveprocess spawns aggressively during testing viaSQLiteVectorManager, maxing out the CPU and failing memory insertions (dimension mismatch errors).This ticket tracks temporarily reverting the config back to
engine: 'chroma'until the local SQLite vector engine and dependency booting logic is further polished. Let's switch it back for stability.