SLADE icon indicating copy to clipboard operation
SLADE copied to clipboard

Crash on opening any WAD on Windows 10

Open schmidtzoltan opened this issue 3 years ago • 5 comments

SLADE Version: 3.2.1 (x64) Operating System: Windows 10 (build 19043), 64-bit edition

Issue Details: when I try to open any WAD with SLADE, a crash occurs with this stack trace:

Version: 3.2.1 (x64)
Current action: aman_open
Operating System: Windows 10 (build 19043), 64-bit edition
Graphics Vendor: OpenGL not initialised
Graphics Hardware: OpenGL not initialised
OpenGL Version: OpenGL not initialised

Stack Trace:
0: [unknown location] RaiseException
1: [unknown location] stw_unbind_context
2: [unknown location] stw_unbind_context
3: [unknown location] stw_unbind_context
4: [unknown location] [unknown:3208088318]
5: [unknown location] stw_init_screen
6: [unknown location] DrvDescribePixelFormat
7: [unknown location] wglCopyContext
8: [unknown location] wglSwapMultipleBuffers
9: [unknown location] wglCopyContext
10: [unknown location] wglGetPixelFormat
11: [unknown location] wglSetPixelFormat
12: [unknown location] SetPixelFormat
13: [unknown location] LibRaw::rgb_to_lch
14: [unknown location] LibRaw::rgb_to_lch
15: [unknown location] LibRaw::rgb_to_lch
16: [unknown location] std::unique_ptr<std::basic_streambuf<char,std::char_traits<char> >,std::default_delete<std::basic_streambuf<char,std::char_traits<char> > > >::get
17: [unknown location] std::unique_ptr<std::basic_streambuf<char,std::char_traits<char> >,std::default_delete<std::basic_streambuf<char,std::char_traits<char> > > >::get
18: [unknown location] std::unique_ptr<std::basic_streambuf<char,std::char_traits<char> >,std::default_delete<std::basic_streambuf<char,std::char_traits<char> > > >::get
19: [unknown location] std::unique_ptr<std::basic_streambuf<char,std::char_traits<char> >,std::default_delete<std::basic_streambuf<char,std::char_traits<char> > > >::get
20: [unknown location] std::unique_ptr<std::basic_streambuf<char,std::char_traits<char> >,std::default_delete<std::basic_streambuf<char,std::char_traits<char> > > >::get
21: [unknown location] std::unique_ptr<std::basic_streambuf<char,std::char_traits<char> >,std::default_delete<std::basic_streambuf<char,std::char_traits<char> > > >::get
22: [unknown location] std::unique_ptr<std::basic_streambuf<char,std::char_traits<char> >,std::default_delete<std::basic_streambuf<char,std::char_traits<char> > > >::get
23: [unknown location] LibRaw_abstract_datastream::subfile_open
24: [unknown location] LibRaw_abstract_datastream::subfile_open
25: [unknown location] std::unique_ptr<std::basic_streambuf<char,std::char_traits<char> >,std::default_delete<std::basic_streambuf<char,std::char_traits<char> > > >::get
26: [unknown location] std::unique_ptr<std::basic_streambuf<char,std::char_traits<char> >,std::default_delete<std::basic_streambuf<char,std::char_traits<char> > > >::get
27: [unknown location] LibRaw_abstract_datastream::subfile_open
28: [unknown location] LibRaw_abstract_datastream::subfile_open
29: [unknown location] LibRaw::rgb_to_lch
30: [unknown location] LibRaw::rgb_to_lch
31: [unknown location] LibRaw::rgb_to_lch
32: [unknown location] LibRaw::rgb_to_lch
33: [unknown location] LibRaw::rgb_to_lch
34: [unknown location] LibRaw::rgb_to_lch
35: [unknown location] LibRaw::rgb_to_lch
36: [unknown location] LibRaw::rgb_to_lch
37: [unknown location] LibRaw::rgb_to_lch
38: [unknown location] LibRaw::rgb_to_lch
39: [unknown location] LibRaw::rgb_to_lch
40: [unknown location] LibRaw::rgb_to_lch
41: [unknown location] LibRaw::rgb_to_lch
42: [unknown location] LibRaw::rgb_to_lch
43: [unknown location] LibRaw::rgb_to_lch
44: [unknown location] CallWindowProcW
45: [unknown location] DispatchMessageW
46: [unknown location] LibRaw::rgb_to_lch
47: [unknown location] LibRaw::rgb_to_lch
48: [unknown location] LibRaw::rgb_to_lch
49: [unknown location] LibRaw::rgb_to_lch
50: [unknown location] LibRaw::rgb_to_lch
51: [unknown location] LibRaw::rgb_to_lch
52: [unknown location] LibRaw::rgb_to_lch
53: [unknown location] BaseThreadInitThunk
54: [unknown location] RtlUserThreadStart

Last Log Messages:
Base resource loaded
Loading game configurations
SLADE Initialisation OK
Error: Can't open registry key 'HKLM\Software\Wow6432Node\GOG.com' (error 2: A rendszer nem találja a megadott fájlt.)
Error: Can't read value of 'HKLM\Software\Wow6432Node\GOG.com\DefaultPackPath' (error 2: A rendszer nem találja a megadott fájlt.)
Checking for updates...
Latest stable release: v3.2.1
Latest beta release: v3.2.0 beta 4
Already up-to-date
Opening archive C:\Program Files (x86)\Steam\steamapps\common\Doom 2\base\doom2.wad

the device I'm using is a Lenovo Thinkpad T510 laptop with relatively untouched Windows 10 install. The strange thing is that I'm using a dual boot setup with Manjaro, and on Manjaro, after some minor changes, I could compile SLADE from scratch and use it without any issue or crash so far.

In any other case I'd assume something's wrong on my behalf - and it still might be case, given the lackluster featuring of my integrated GPU. But since this thing runs on a Linux setup flawlessly, especially on a distro you likely haven't tested, I can't help but ask if you have any idea, what's going on in my case?

I installed Mesa 22.1.7 and I tried using it to provide OpenGL features I'm lacking but so far it couldn't save any applications I've had so far, and SLADE is no exception-

I also admit it might be an edge case in which I'm attempting to use SLADE on a heavily deprecated, old machine, but I think if you have a solution for it, or maybe even I can help with it, it can improve SLADE even more.

schmidtzoltan avatar Aug 30 '22 20:08 schmidtzoltan

I might be having the same issue. I'm using DRD Team's debian package.

Version: 3.2.1
No current action

Operating System: Linux 5.15.0-46-generic x86_64
Graphics Vendor: Intel
Graphics Hardware: Mesa Intel(R) HD Graphics 500 (APL 2)
OpenGL Version: 4.6 (Compatibility Profile) Mesa 22.0.5

Stack Trace:
0: [unknown location] wxLogger::DoLogWithNum(long, wchar_t const*, ...)
1: [unknown location] [unknown:139895409085191]
2: [unknown location] [unknown:139895379174688]
3: [unknown location] slade::web::getHttp(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
4: [unknown location] std::error_code::default_error_condition() const
5: [unknown location] [unknown:139895379512131]
6: [unknown location] [unknown:139895380109824]

Last Log Messages:
Setting up the OpenGL context
Initialising OpenGL...
OpenGL Version: 4.6
Max Texture Size: 16384x16384
Checking extensions...
Vertex Buffer Objects supported
Point Sprites supported
Framebuffer Objects supported
Opening map map01
Removed 0 detached vertices, 0 detached sides, 0 invalid sides and 0 detached sectors

ANN-4-BE-11-A avatar Aug 30 '22 23:08 ANN-4-BE-11-A

Unlikely the same issue, Ann. The trace above mentions not being able to open registry keys for the GOG version of the Doom, which is pretty much a Windows thing and you are using Linux. Your stack trace seems to also be much shorter and mentions different parts of code. Your stack trace seems to have to do with some web code Slade uses?

darkhog avatar Sep 11 '22 10:09 darkhog

I think my issue may have had something to do with the name of the map I was working with. It had more than 8 characters. Maps with 8 or less characters didn't lead to the same issue. But that's just a hypothesis. I don't have Slade to test it and I wouldn't even if I did. I gave up on Doom modding. Feel free to ignore my issue.

ANN-4-BE-11-A avatar Sep 13 '22 13:09 ANN-4-BE-11-A

@ANN-4-BE-11-A no, if this issue exists then it should be fixed. Name handling has issues anyways because beyond the bug I mentioned above, the loading of a WAD also fails when its path contains special characters like é, ő, or ö.

So there are things to do; actually I'd fix them personally if I had the time.

@darkhog surreal indeed, I tried making progress by adding regedit keys but somehow it wasn't enough. I really don't want to spend money on the GOG versions just to be able to run SLADE especially since I own the entire anthology on Steam.

schmidtzoltan avatar Sep 13 '22 19:09 schmidtzoltan

I guess so. I thought that it was a me issue, given that I have a tendency to break things and the consequences only affect me. But I suppose this isn't one of those cases. I won't do any testing, but I can provide additional info on request, such as specs.

ANN-4-BE-11-A avatar Sep 14 '22 14:09 ANN-4-BE-11-A

I have no idea what the original crash could be unfortunately, judging by the stack trace it's in the graphics driver but that's about all I can say.

The registry key errors can be safely ignored, they are just generated when searching for commonly installed iwads (gog/steam/etc.) and shouldn't affect anything, you will just need to manually set the paths to iwads in the base resource settings.

sirjuddington avatar Nov 07 '22 08:11 sirjuddington

Can, or should I provide any extra log, or stack trace that can help you understand more?

To be honest, at this point I'm also very curious because it's rare that something runs on Linux but not for Windows, usually it's the other way around. I also highly doubt it's a hardware issue.

schmidtzoltan avatar Nov 07 '22 08:11 schmidtzoltan