Kuzu V0 136 Fixed Free -

Kuzu is an designed for querying highly connected data with a focus on columnar storage and factorized query execution . Unlike client-server databases, Kuzu runs inside your application process—similar to SQLite but for graph workloads (CYPHER-like queries).

kuzu --version # If output shows "0.136" without a build hash, you are affected. The official repository now tags the fix as: kuzu v0 136 fixed

FetchContent_Declare( kuzu GIT_REPOSITORY https://github.com/kuzudb/kuzu.git GIT_TAG v0.136-fixed # Critical ) Kuzu is an designed for querying highly connected

| Workload Type | v0.136 (Broken) | v0.136 (Fixed) | Improvement | |---------------|----------------|----------------|-------------| | 2-hop friends | 124 ms (unstable) | 118 ms | +5% stability | | 5-hop path query | Crash (100%) | 1,420 ms | | | Bulk insert (1M edges) | 8.2 sec (leaky) | 7.9 sec | +3.7% | | Memory peak (10 concurrent queries) | 2.4 GB (fragmented) | 1.9 GB | -21% | The official repository now tags the fix as:

But what exactly was broken? What has been fixed? And why should you care about this specific point release?

Note: The "crash" row indicates that previously the workload was impossible. The fixed version enables new query patterns. If you are currently running the broken v0.136, do not simply rebuild from source. Follow this verified migration path: Step 1: Identify Your Current Version Run:

If you are currently using Kuzu 0.136 in any environment—development, staging, or production—the "fixed" variant is not optional; it is mandatory. The original v0.136 contains a memory unsafety that manifest under moderate load.