[Fixed] Another crash on aborting network game

[Player701]

NB: not a duplicate. From here, since the old thread is apparently not going to be reopened. Tested in GZDoom g4.9pre-71-g67127e4cc.

Running gzdoom -join localhost and then clicking on "Abort Network Game" crashes with an access violation on this line (TMap<FName,FBaseCVar * __ptr64,THashTraits<FName>,TValueTraits<FBaseCVar * __ptr64> >::CheckKey(...) returned nullptr). Call stack:



In addition to the above, aborting network games in both -host and -join modes triggers an assertion failure here with the following call stack:



The assertion failure does not manifest in release builds but is visible in a debugger.

[Graf Zahl]

Fixed the assert. The quit message from the startup screen was not being properly processed and did not quit immediately. I wonder what change made this break now - from the looks of it this should always have caused problems.
The other bug just looks like a follow up of not quitting right away.

[Player701]

Both issues seem to be gone now, thanks.