When managing large-scale, high-concurrency OpenResty/LuaJIT services, many seasoned architects have encountered a perplexing and counter-intuitive challenge: while the service’s business logic operates robustly and Lua VM-level garbage collection (GC) data indicates normal operation, operating system monitoring tools consistently show an irreversible, continuous increase in the process’s Resident Set Size (RSS). This peculiar phenomenon, an apparent “leak” that isn’t a logical one, often looms ...