suprepupre/wow-optimize v3.5.11

wow_optimize v3.5.11

on GitHub

wow_optimize v3.5.11

This release focuses on stability fixes for real gameplay regressions: an occasional multi-client relog crash, a loading/teleport out-of-memory
crash around M2Shared.cpp:267, and a last-minute production hotfix for CRT fast paths.

Fixed

• Fixed an occasional crash when multiple clients are open and one client returns to character select, then enters the world on another character. - Fixed a loading / teleport OOM path that could show:
  • M2Shared.cpp
  • Line: 267
  • Not enough memory resources are available to process this command

Stability

• Lua VM reload handling now waits for the new lua_State to settle before reinitializing allocator and GC state.
• Loading transitions now trigger an earlier memory trim when Lua memory is already high.
• Addon loading-state polling is now more aggressive on slow or high-memory frames so loading-mode protections engage earlier.
• Reload reinit now also resets stale combat / idle / loading flags on confirmed Lua VM switches.

Hotfix

• CRT memory/string fast paths are included in the build system, but remain disabled in the public build.
• An enabled production build caused an immediate client exit after pressing Enter to enter the world.
• These hooks will stay disabled until they are isolated and bisected properly.

Build artifacts

• wow_optimize.dll
• version.dll
• wow_loader.exe

Installation

Proxy load:

• Copy version.dll and wow_optimize.dll into the WoW folder, then launch WoW normally.

Loader:

• Copy wow_loader.exe and wow_optimize.dll, then launch wow_loader.exe.

Manual injection:

• Copy wow_optimize.dll and inject it after WoW starts.

Notes

• Public-safe feature configuration remains unchanged.
• Historically unsafe hooks remain disabled.
• GetEnvironmentVariableA cache stays disabled.
• CRT fast paths also stay disabled in this release.