+-----------------------------------------------------------+ | Application Layer | +-----------------------------------------------------------+ | v (In-Process Call) +-----------------------------------------------------------+ | Kùzu v0.13.6 Engine | | | | +--------------------+ +-----------------------+ | | | Vectorized Query | | Columnar Storage | | | | Execution | ------>| Engine (Disk/Memory) | | | +--------------------+ +-----------------------+ | | | | | | v v | | +--------------------+ +-----------------------+ | | | Factorized Joins | | Structured Sparse | | | | & WCO Algorithms | | Rows (CSR Adjacencies)| | | +--------------------+ +-----------------------+ | +-----------------------------------------------------------+ High-Performance Structural Traits YouTube·The Geek Narrator The Future of Graph Databases (w/ The Founder of KuzuDB)
Key commit message: "Fix stack corruption in variable-length path expansion for 'kuzu v0.136 fixed' – clone iterator on fork."
Memory boundaries between Javascript's V8 engine and Kùzu's underlying C++ memory blocks are now safely guarded against unaligned memory access patterns. Performance Impact: What Developers Will Notice Metric Focus Area Prior Versions (v0.12.x / Early v0.13) Fixed Status in v0.13.6 Bulk Rollbacks Potential for OverflowFile corruption. Safely merged free pages; transactional safety guaranteed. Vector Index Updates Gradual heap memory accumulation. Immediate heap cleanup on index changes. Deep Cypher Joins Uncapped memory spikes on higher core counts. Thread-aware resource limits prevent crashes. Rust Multi-threading Potential QueryResult iterator lockups. Predictable, fully thread-safe execution. Migration and Upgrading Guidelines
Steps: pip uninstall kuzu && pip install kuzu==0.136.1 kuzu v0 136 fixed
To check if your current installation matches the "fixed" version you are looking for, run: import kuzu print(kuzu.version) Use code with caution. Copied to clipboard 5. Troubleshooting Specific Bugs
Once these steps are complete, your existing component validation will continue to work as before, now powered by Pydantic.
Kùzu is an in-process, embedded property graph database designed for speed and scalability. While the project has been archived as of late 2025, recent releases—specifically leading up to and including —focused on critical stability fixes and advanced query capabilities. Key Technical Improvements Vector Index Updates Gradual heap memory accumulation
On highly threaded processors (such as 64-core and 128-core servers), the execution planner occasionally calculated sub-optimal join orders when analyzing multi-label variable-length paths. This mistake led to thread starvation and elevated memory usage spikes.
#KuzuDB #GraphDatabase #DataEngineering #OpenSource
Where v0.135 felt like a beta product, v0.136 fixed exudes the confidence of a production-grade system. The careful attention to cross-platform details, the transparent changelog, and the rigorous benchmarking show a maturing project ready for wider enterprise adoption. Thread-aware resource limits prevent crashes
🐘
Optimized how ownership of transactions is handled within the TransactionManager to prevent memory leaks during long-running sessions. Platform Compatibility: