Open kortemik opened 8 years ago
in RBDoom3BFG I don't get that error:
]developer 1
]crash
writing to: /home/biel/.rbdoom3bfg/base/consoleHistory.txt
signal caught: Illegal instruction
si_code 2
Trying to exit gracefully..
session->GetSaveGameManager().CancelToTerminate();
soundSystem->StopAllSounds();
Stop();
--------- Game Map Shutdown ----------
--------------------------------------
CleanupShell();
delete loadGUI;
delete renderWorld;
delete soundWorld;
delete menuSoundWorld;
session->ShutdownSoundRelatedSystems();
session->Shutdown();
game->Leaderboards_Shutdown();
uiManager->Shutdown();
soundSystem->Shutdown();
AL lib: (WW) FreeDevice: (0x7986100) Deleting 262 Buffer(s)
usercmdGen->Shutdown();
eventLoop->Shutdown();
declManager->Shutdown();
renderSystem->Shutdown();
idRenderSystem::Shutdown()
Shutting down OpenGL subsystem
commonDialog.Shutdown();
UnloadGameDLL();
------------ Game Shutdown -----------
--------- Game Map Shutdown ----------
--------------------------------------
Shutdown event system
--------------------------------------
saveFile.Clear( true );
stringsFile.Clear( true );
CloseLogFile();
fileSystem->Shutdown( false );
Sys_Shutdown();
console->Shutdown();
idKeyInput::Shutdown();
cvarSystem->Shutdown();
cmdSystem->Shutdown();
ClearWarnings( GAME_NAME " shutdown" );
warningCaption.Clear();
errorList.Clear();
idLib::ShutDown();
shutdown terminal support
biel@Biel-laptop:/usr/local/share/d3bfg$
So you're surprised that the game crashes when you crash it? And that one crash gets it into a flakey state so other crashes follow later? ...
I am not surprised by that, it should come down cleanly as the sig_handler is bringging the live engine down. sigill is being handled and because of that it should come down as cleanly as with sigquit. openal seems to skip some checks.
it wont happen on rbdoom3 as their assets have sounds playing from startmenu onwards we don't have that.
On Tue, Jul 19, 2016 at 5:39 PM, Daniel Gibson notifications@github.com wrote:
So you're surprised that the game crashes when you crash it? And that one crash gets it into a flakey state so other crashes follow later? ...
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/OpenTechEngine/OpenTechBFG/issues/108#issuecomment-233653634, or mute the thread https://github.com/notifications/unsubscribe-auth/AA19Ommwxxqum1mL2YXRCVSC94Pr7MfCks5qXOGHgaJpZM4JPxWn .
those this happen to do with "com_smp" ?
... entered "developer 1" and "crash" on the console:
as expected. But later: