← Back
Luajit

Fix LuaJIT RSS Memory Leak in OpenResty: Stop OOM Kills Without Restarts

  • What Is the LuaJIT Pseudo Memory Leak?
  • Diagnosing the Problem with Real Production Data
  • Why Standard Fixes Don’t Work
  • How LuaJIT-plus Fixes This at the Allocator Level
  • Production Impact After Deployment
  • What Is the LuaJIT Pseudo Memory Leak?
  • Diagnosing the Problem with Real Production Data
  • Why Standard Fixes Don’t Work
  • How LuaJIT-plus Fixes This at the Allocator Level
  • Production Impact After Deployment

Automatic Core Dump Analysis (using OpenResty XRay)

  • Locate the core dump file from a crashed OpenResty/Nginx worker
  • Start automatic (guided) core dump analysis in OpenResty XRay
  • Read the signal, CPU registers, and C backtrace of the crash
  • Follow the Lua backtrace to the exact crashing line
  • Automatic Insights reports for online core dumps
  • Locate the core dump file from a crashed OpenResty/Nginx worker
  • Start automatic (guided) core dump analysis in OpenResty XRay
  • Read the signal, CPU registers, and C backtrace of the crash
  • Follow the Lua backtrace to the exact crashing line
  • Automatic Insights reports for online core dumps

LuaJIT GC64 Mode: Removing the 2GB Memory Limit

  • The Old Memory Limit
    • When Hitting The Memory Limit
    • The Memory Limit Is Per Process
    • GC-Managed Memory
    • Memory Allocated Outside GC
    • Extending The x64 Mode to The 4 GB Limit
  • The New GC64 Mode
    • How to Enable The GC64 Mode
    • Performance Impact
    • Debugging and Profiling Tool Chains
  • The Old Memory Limit
    • When Hitting The Memory Limit
    • The Memory Limit Is Per Process
    • GC-Managed Memory
    • Memory Allocated Outside GC
    • Extending The x64 Mode to The 4 GB Limit
  • The New GC64 Mode
    • How to Enable The GC64 Mode
    • Performance Impact
    • Debugging and Profiling Tool Chains
Contact us

Love to hear from you, Get in touch 👋

Message was sent successfully!

Our Team will get back to you within 24 hours.
x