Status: I'm unable to reproduce this myself, but since multiple people have reported it, I figure it's not an isolated issue from an unusual setup. I've changed how the game handles exiting when Cancel is clicked, and this should hopefully prevent issues. I sent a test version out to a few people; all of them either said the crash no longer occurs, or didn't respond at all (so I'm assuming no news is good news). If you did have this bug, and weren't sent a test version, just try with the newest experimental release. Until / unless I hear otherwise, I'm assuming this bug is fixed.
Start NeoLemmix.exe and instead of loading a level or a level pack, use the Cancel button (or the litle cross in the top right corner). Then I get an error message (loosely translated from German to English):
"NeoLemmix. exe does not work any more. Due to a problem, the program cannot work properly. Please close the program."
And one gets this error message twice!
Quote from: Nepster on January 23, 2016, 09:03:30 AM
Start NeoLemmix.exe and instead of loading a level or a level pack, use the Cancel button (or the litle cross in the top right corner). Then I get an error message (loosely translated from German to English):
"NeoLemmix. exe does not work any more. Due to a problem, the program cannot work properly. Please close the program."
And one gets this error message twice!
Tested it and it's the same here. Not really game breaking stuff, but a little annoying nevertheless.
I don't get that error message [windows 7]. When I press cancel the program just closes. Is this supposed to happen?
The program is supposed to just close; some of the pre-V1.37n test versions might have crashed instead.
IchoTolot - you use German language settings too, right? Whereas you don't, mobius? I would think it's weird that this makes a difference, but it's the one thing I notice in common between the PCs this does happen on.
Tested it in Wine, 1.38 crashes/segfaults/gives the standard Wine segfault error, "has encountered a serious problem and needs to close." Closing that, another popup comes: Runtime error 216 at 008041CE. The shell is a little more informative:
Backtrace:
=>0 0x005c5774 (0x0100ea68)
1 0x7bc71d88 call_thread_func+0xb() in ntdll (0x0100ea78)
2 0x7bc71f60 call_thread_entry_point+0x6f(entry=0x5e0fc6, arg=0x0(nil)) [/home/simon/c/notown/wine-1.3.17/dlls/ntdll/signal_i386.c:2499] in ntdll (0x0100eb48)
3 0x7bc7bad9 start_thread+0xe8(info=0x7ffd0fb8) [/home/simon/c/notown/wine-1.3.17/dlls/ntdll/thread.c:404] in ntdll (0x0100f398)
4 0xf75aa955 start_thread+0xb4() in libpthread.so.0 (0x0100f498)
-- Simon
Quote from: namida on January 24, 2016, 01:34:11 AM
The program is supposed to just close; some of the pre-V1.37n test versions might have crashed instead.
IchoTolot - you use German language settings too, right? Whereas you don't, mobius? I would think it's weird that this makes a difference, but it's the one thing I notice in common between the PCs this does happen on.
Yes, I use the German language setting. This would be very weird if that's the cause here ;P
@möbius: Do you use the latest version V1.37B or the original V1.37?
I tried this bug on the original V1.37 release and the game closes without any error message. However starting with the experimental release NeoLemmix_V1.37n-B_1601170256.exe I get the error.