Closed Jake3231 closed 7 years ago
Does it crash with multicore rendering completely disabled? ( restart the game after you toggle it )
Does it only crash when you get shot? ( Try using bots to shoot at you, try shooting bots )
Can you attach a console log with developer 2
enabled at the moment of the crash? ( Use log to file )
Also use external paste tools for these huge logs.
I was able to cause the issue to stop occurring after I disabled multicore rendering. I first launched the game, then used Shift+tab to open the console, then entered the following command: gmod_mcore_test 0; mat_queue_mode 0; cl_threaded_bone_setup 0
After doing this, being shot by combine soldiers did not crash the game.
nvm
Okay. I saw your question, and the latest build (2017.03.19) did not resolve the issue. I've uploaded another crash log here if it would help. I've noticed that every time the crash occurs, the game is using about 2.2GB of memory. It seems like a bit much after just spawning a few NPCs.
Never mind my question, I thought it might have been caused by my changes to prevent decal crashes, but then I was reminded that that change is already in Live version of the game.
Okay. Is there any other information I can collect to help solve this issue?
This should be fixed. Please let me know if this still occurs after the dev branch has updated (no more than 30 minutes from now). The proper way to reproduce it is to just shoot at a prop. Make sure you've got:
gmod_mcore_test 1
mat_queue_mode -1
studio_queue_mode 1
The problem seem to be resolved. I enabled multicore, then allowed the player to be shot by NPCs, as well as shoot a prop myself. Both situations no longer trigger a crash.
Details
When opening a game on the latest dev build (2017.03.18), I've found that when some NPCs fire weapons the game crashes. This only occurs on the dev branch, and not on the release branch. I've tested both versions on a 2015 MacBook Pro running OS X 10.11.6, but I have not tested on Windows. Below is a crash log.
Steps to reproduce: