Can't run 64-bit Minetest 5.9 on 64-bit Windows 10

[ThePython10110]

Minetest version

Minetest 5.9.0-70bddcf (Windows)
Using LuaJIT 2.1.1706185428
Built by Clang 17.0
Running on Windows/10.0.19041 x86_64
BUILD_TYPE=Release
RUN_IN_PLACE=1
USE_CURL=1
USE_GETTEXT=1
USE_SOUND=1
STATIC_SHAREDIR="."
STATIC_LOCALEDIR="locale"

Also Minetest-5.9.0-c63c05b

Irrlicht device

WIN32

Operating system and version

Windows 10

CPU model

Intel Core i7-6700

GPU model

Intel HD Graphics 530

Active renderer

OpenGL 4.6.0

Summary

Trying to run sfan5's builds of Minetest 5.9.0, I noticed that the 64-bit builds crashed immediately when trying to run them, but the 32-bit builds seemed to work fine (although loading blocks seems to take a lot longer than I'm used to). It gives error code -1073741819, if that helps.

I would build it myself if I could, but I can't seem to make that work either.

If it's just a problem with my computer... that's annoying, but not entirely unexpected.

Steps to reproduce

1. Download and extract one of the two most recent 64-bit builds from here. I haven't tested with any others, so they might also work.
2. Run it.
3. Instant crash.
4. Download the 32-bit build.
5. No crash, but laggy.

[ThePython10110]

I managed to build it myself, and that worked fine. I guess I'll close this now.

[sfan5]

My builds are very close to the official builds, so it's likely that this problem affects both.
Please try the "mingw64" one from here.

[ThePython10110]

It doesn't work and give the same error code. When running in MINGW, it says "segmentation fault." I managed to build it with MSYS/Clang, and that worked fine for me.
I didn't do anything special; just followed this exactly.

[SmallJoker]

Would you please be so nice to provide a backtrace of the failing build by running it inside gdb or lldb? If those binaries are found in %PATH%, you could start Minetest as follows: minetest.exe --debugger. Otherwise C:\path\to\gdb.exe --args minetest.exe, then r and finally bt after crash.

[ThePython10110]

Weird. It actually runs fine when running it via GDB, but not when I just launch it.

[ThePython10110]

This may be a duplicate of #14665

[sfan5]

It gives error code -1073741819, if that helps.

That's just 0xc0000005, so a segfault.

This may be a duplicate of #14665

Unlikely IMO, the other looks like a macOS-specific issue.

[ThePython10110]

This may be a duplicate of #14665

Unlikely IMO, the other looks like a macOS-specific issue.

Yeah, I only said that because it matched what I was seeing exactly.

[SmallJoker]

@ThePython10110 Would you please be so nice to use an older 5.9.0-dev build to see which is the first one to crash? At least that would help us to narrow down the range of commits since 5.8.0.

[waxtatect]

I can't reproduce the instant crash, tested current latest, minetest-5.9.0-36d236c-win64.7z, also 70bddcf and c63c05b in 64-bit with Windows 10. Only obvious thing i noted, minetest starts with touch screen enabled, yet my laptop has no touch screen... but that works normally anyway once manually disabled

[ThePython10110]

431444b works, but not 8cbd629.