Error 132 on WoW.exe launch, Linux Mint

[Valeriasht]

Log included attached to linked bug report.

Bug report here: https://github.com/OxLlamaLinOct/octola ... x/issues/1

When launching with the Octo-Wow launcher (octowowlauncher-linux), error seen in image below is produced.

octo-WoW.png (80.21 KiB) Viewed 2091 times

[Sadstare]

Both myself and friend having similar issue on windows today after working earlier?

[Valeriasht]

This is happening on Linux Mint via the above-linked Octowowlauncher-Linux, specifically.

[Alexander90802]

Update (for anyone using the unofficial OctoLauncher Linux rebuild, not the official client): this is fixed as of the latest release (v1.3.10).

Turned out to be a genuine race condition in the WoW.exe client itself — one of its own startup routines isn't properly thread-safe, and it practically never loses that race on typical desktop CPUs, but higher-core-count hardware changes the timing enough to hit it reliably. The launcher now automatically pins the game to a single CPU core to work around it, which is safe since the 1.12 client never needed more than that anyway. No settings to change, it's on by default.

Grab the latest build of the unofficial launcher here: https://github.com/OxLlamaLinOct/octola ... ses/latest

[Kaon]

Turn off DXVK in the mods.

[Kolvin]

Attempted using the appimage posted. Launcher blinks in and out, but will not run WoW.exe.

Running WoW.exe directly from lutris or wine gives me that same 132 error.



Works OK now on my windows 11 mini PCs when I adjust to laptop settings.

[Zeitghost]

I am getting the same error and before game crashes, plainstriders in Mulgore aren't rendering properly. Just the plainstriders, both normal and elder. They look like the acid spitters from Silent Hill. I've cleared addons and WDB and I've never had any of the octoWoW mods active, so nothing to disable there.