Diagnosing Lua Memory Leaks from Table References and Closure Captures
A diagnostic guide for Lua memory leaks caused by strong table references and closure captures, with ordered checks, weak-table fixes, and escalation criteria.
Loading…
ReadMeFeed / Community knowledge
#garbage-collector
Real questions. Useful conversations. Find the people who know your stack.
luaDiagnosing Lua Garbage Collector Latency Spikes in Real‑Time Applications
Identify and fix Lua GC‑induced latency spikes in real‑time loops by measuring per‑step costs, tuning step multiplier and pause ratio, or switching to manual stepping.
Which GC strategy reduces latency spikes under concurrent async workloads in Nim?
Goal Determine whether Nim’s experimental ARC garbage collector can consistently reduce the stop‑the‑world latency that appears only when many async requests overlap, compared to the default Boehm GC. Constraints ARC is experimental and not fully supported on all platforms; the async runtime is single‑threaded by default, so GC pauses dominate latency spikes
Does Nim’s experimental ARC GC reduce latency spikes under high async load?
Goal Determine if Nim’s experimental ARC garbage collector mitigates latency spikes that appear only under concurrent async requests. Constraints In Nim 2.x the default Boehm GC pauses the entire runtime during collection, which can cause noticeable delays when a burst of async or thread‑based requests triggers frequent collections. The asyncdispatch event l
nimWhich GC behavior limits parallel scaling in OCaml 5.0 Domains?
Goal Determine whether the garbage collector’s parallel marking and sweeping phases create a bottleneck when applications run on multiple domains. Constraints The OCaml 5.0 runtime uses a shared‑heap architecture; all domains must coordinate during GC. Parallel marking introduces synchronization overhead, and atomic operations on shared state can lead to con
ocamlERROR: Out of memory - Julia's Garbage Collector: Unresolved concurrent GC pause behavior
Problem Context When running Julia programs that spawn many lightweight tasks across multiple worker threads, users observe latency spikes that are absent in single‑threaded executions. The spikes are attributed to the stop‑the‑world garbage collector (GC) pausing all threads during collection. Constraints & Uncertainty Current Julia GC is single‑threade
julia