[Ninety-Six]

I may be entirely on the wrong track here but after I installed the 10/13 update, Polymost has led to fatal eduke hang-ups. This runs the gambit from the newest eduke revisions (which chug on this computer anyway), to older ones such as r7140 (which actually run fine on this machine). About one whole second after the main menu loads, eduke completely hangs up. I have to bring up task manager, which actually doesn't even show up but it uncaptures the mouse which allows the error reporting service to blank it out and ask if it should end the program. That's the only way out.

I want to note that classic runs just fine. No issues.

There are logs and config files from this post, using the debug version of 7140.

I want to emphasize that the day before the update, there was no issues whatsoever. I changed nothing in the installation folder, and I even experimented with the eduke file to see if the recorded level times or permanent upgrades broke something. They didn't. And then I installed Demon Throne, fresh from the box in its own separate directory. Loaded up the provided revision in 32-bit mode because I heard there was supposed to be a unique intro cutscene that I wanted to watch before switching to classic, and it hung a second after the title map loaded.



I know the update refers to something about virtual machines and I don't see anyone else reporting this issue, so I could very well be entirely wrong. If so, consider this a "standard" bug report. But all the same, that is literally the only thing that changed between the day it worked fine, and the day it started to fatally hang. I didn't even download anything new, let alone install (short of a drive-by download at least, but I have noscript running so it's unlikely. Not impossible, mind.)

And if it is the update I don't have any system restore points I can use, unless they were created automatically.

[Danukem]

There is scattered but increasing evidence that the windows update is causing eduke32 crashes. It would explain why we started getting a crash on a certain map after release but the same map never crashed before that. The eduke version didn't change, only one line of CON code which would be completely irrelevant.

[oasiz]

I started getting issues in mapster where it would corrupt floor/ceiling textures even on classic when using 2D/3D preview about 1-2 months ago.
It would also cause instabilities.

The moment I renamed "mapster32.exe" to "napster32.exe" the issues disappeared.
10/10 fun, would debug again.

MS Defender ?

[jkas789]

Can also report that this has happened to me as well.

[Doom64hunter]

oasiz, on 16 October 2020 - 12:53 PM, said:

I started getting issues in mapster where it would corrupt floor/ceiling textures even on classic when using 2D/3D preview about 1-2 months ago.
It would also cause instabilities.

The moment I renamed "mapster32.exe" to "napster32.exe" the issues disappeared.
10/10 fun, would debug again.

MS Defender ?

That sounds oddly enough very much like that issue recently posted in the DNF 2013 thread in this subforum.

In WGR2 we have also encountered several freezes that could be traced back to the Windows MME music playback. Backtraces of this are available on the Issues page on voidpoint.io

And finally, I also encountered persistent crashes when loading a save, which were magically solved by moving the save files out of the eduke32 folder and then back into it.
I've never encountered so much weird shit as in the last 2 months.

[Ninety-Six]

Okay so I want to issue a small correction. Anyone who read the page probably already knows this, but I misread all the headers of that page. The virtual machine stuff isn't relevant to the actual update. The actual update seemed to be pretty minor as far as I can tell? But nonetheless the fatal hangings started after the update.


I don't know if it helps anything at all but it's here if it helps anyone figure this out anyway.

[Doom64hunter]

Danukem, on 16 October 2020 - 12:39 PM, said:

There is scattered but increasing evidence that the windows update is causing eduke32 crashes. It would explain why we started getting a crash on a certain map after release but the same map never crashed before that. The eduke version didn't change, only one line of CON code which would be completely irrelevant.

Doom64hunter, on 16 October 2020 - 10:37 PM, said:

And finally, I also encountered persistent crashes when loading a save, which were magically solved by moving the save files out of the eduke32 folder and then back into it.

It turns out that this is the exact same crash. I first encountered the problem on September 12th, but back then I attributed the problem to loading outdated saves, which I know now is not the case.
If this is a Windows problem, then the update must have occurred sometime before that date.