Kuzu V0 136 - Fixed

Kùzu v0.1.3.6 update is a targeted stability release for the embedded property graph database. This minor version focuses on resolving resource management issues to ensure reliability during high-load operations. Core Fixes in v0.1.3.6 Memory Management : Addressed specific small memory leaks

Processes data in chunks (vectors) to maximize CPU cache locality and hardware efficiency. Key Fixes and Improvements in v0.13.6

MATCH (a:Person)-[:KNOWS*1..5]->(b:Person) WHERE a.id = 136 RETURN b.name

Kùzu's engine constantly undergoes refinement to handle complex, multi-hop queries.

Columnar disk-based storage with compressed sparse row-based (CSR) adjacency lists. kuzu v0 136 fixed

Below is a blog post summarizing the recent critical fixes and the current status of the project, including the 2025 archiving announcement. Kùzu Update: Recent Fixes and the State of the Graph

In v0.135, users reported linear memory growth during long-running operations. After 48 hours of continuous use, the Kuzu process would consume upwards of 12GB of RAM, eventually crashing the host system. The root cause was traced to a dangling pointer in the buffer pool’s eviction policy. this by rewriting the LRU (Least Recently Used) cache eviction logic, introducing RAII (Resource Acquisition Is Initialization) guards. Early testing shows memory stabilization at under 2GB even after seven days of runtime.

Added support for wildcard patterns in Full-Text Search (FTS) queries and implemented FTS updates.

RETURN length((:Person id: 136)-[:KNOWS*1..4]->(:Person)) AS stability_test; Kùzu v0

A different library entirely (like a specific dataset version for AI). A typo for v0.1.3 or v0.3.6 .

If you are experiencing bugs in an older version, the "fix" is almost always to upgrade to the latest stable build. pip install kuzu --upgrade Use code with caution. Copied to clipboard Using Node.js: npm install kuzu@latest Use code with caution. Copied to clipboard 3. Key Areas Addressed in Recent "Fix" Cycles

Simplifies portability by storing the entire database in one file.

Supports a comprehensive subset of the Cypher query language. Key Fixes and Improvements in v0

Ensure you clean out legacy development cache instances before pulling the fixed library binaries:

In-memory and embedded databases must manage RAM with extreme precision. Previous iterations occasionally suffered from edge-case memory leaks during highly complex recursive joins or massive MERGE operations.

: Significant work went into casting between unions and fixing issues with nested unions and union arrays, providing more flexibility for semi-structured data.