Fix: The new concurrency model defaults to optimistic locking. If you have extremely high write contention, set kuzu.optimistic_retries = 5 in your config file. For pure read-heavy workloads, enable kuzu.read_only = true .
However, version 0.135 introduced several regressions that hampered production use. The core issues ranged from race conditions in multi-threaded environments to a persistent segmentation fault when parsing certain data structures. The community has been eagerly awaiting a stable release, and with , those prayers have been answered. The Critical Bugs Addressed in Kuzu v0.136 Fixed The “fixed” tag in this release is not merely cosmetic. It represents a fundamental overhaul of three major subsystems. Below is a detailed look at the most impactful corrections. 1. The Memory Leak in the Buffer Pool (Issue #892) 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. Kuzu v0.136 fixed 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. 2. Concurrent Write Corruption (Issue #901) Multi-threaded write operations were a nightmare in v0.135. Two threads writing to different segments of the same data structure would occasionally produce torn writes—half of one transaction, half of another. This led to silent data corruption, which is catastrophic for any database or stateful application. kuzu v0 136 fixed
If you have been waiting for a sign to adopt Kuzu—or to return after the v0.135 fiasco—the time is now. Download today, run your workloads, and experience the stability that should have been there from the start. Have you tested Kuzu v0.136 fixed in your environment? Share your results in the comments below or contribute to the official Kuzu GitHub repository. Found another bug? The maintainers are prioritizing reports against this version above all others. Fix: The new concurrency model defaults to optimistic
kuzu v0 136 fixed (primary), Kuzu v0.136 benchmark, upgrade Kuzu, Kuzu memory leak fix, Kuzu concurrency patch, Kuzu JSON parser, Kuzu migration guide. However, version 0
Fix: You likely have a mixed installation. Purge all old libraries: sudo rm -rf /usr/local/lib/kuzu* and reinstall.
Fix: You are trying to load a custom plugin compiled against v0.135. Recompile the plugin against the v0.136 headers.
The release is not just a patch; it is a re-foundation. The three critical memory and concurrency bugs have been eradicated, performance has exceeded pre-regression levels, and the upgrade path is smooth for the vast majority of users. For any team currently stuck on v0.134 or suffering through v0.135, this update is mandatory.
| Service |
 Service one
 Service one
 Service one
|