Kuzu V0 136 Fixed -

The changelog highlights a new optimistic concurrency control mechanism using 64-bit atomic timestamps. The team also removed the problematic spinlock implementation in favor of a mutex pool. Internal stress tests (100 threads performing 10,000 writes each) now show zero conflicts and 99.999% write atomicity. 3. The JSON Parsing Regression (Issue #910) Version 0.135 broke support for nested JSON objects exceeding three levels. Developers relying on Kuzu’s built-in JSON extractor received malformed outputs or outright segfaults. This was particularly painful for those using Kuzu as an ETL (Extract, Transform, Load) tool.

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

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. This was particularly painful for those using Kuzu