Severity: LOW (latent — safe under single-threaded server architecture)
Status: 🟢 FIXED
Files: src/thai.zig:436-498
In src/thai.zig, dynamic loading of libthai is handled via mutable module globals:
var libthai_instance: ?LibThai = null;
var libthai_tried = false;
pub fn getLibThai() ?*const LibThai {
if (!libthai_tried) {
libthai_tried = true;
initLibThai();
}
if (libthai_instance) |*inst| return inst;
return null;
}
Furthermore, initLibThai allocates a single global ThBrk* word-breaker context handle (brk = th_brk_new(null)), and findWordBreaks executes libthai.th_brk_wc_find_breaks(libthai.brk, ...) directly on this shared instance.
getLibThai() nor initLibThai() uses atomic flags or a mutex.th_brk_wc_find_breaks is not documented to be re-entrant when sharing the same ThBrk handle concurrently.szn runs an event-driven, single-threaded server loop (src/server/loop.zig). All terminal handling and grid reflow happen synchronously on the server thread, so this is currently latent.libthai_instance and ThBrk are explicitly single-threaded and bound to the server thread lifecycle.getLibThai() with std.once or atomic initialization.ThBrk per-thread or pass a local context into th_brk_wc_find_breaks.src/thai.zig, replaced unsynchronized libthai_tried boolean with libthai_state: std.atomic.Value(u8) using three-state transitions (uninitialized, initializing, initialized).getLibThai() with atomic compare-and-swap (cmpxchgStrong) and yield spinning, ensuring race-free lazy loading across concurrent threads.getLibThai() documenting the single-threaded server loop contract and future worker guidance.src/thai.zig spawning 4 worker threads concurrently calling getLibThai().