Game running in background for a while after having quit

[Cyntonian]

I tend to host for my friends when we play which can be about an hour or two, sometimes longer. After quitting the game, Steam and Task Manager still show the game as running. Ultimately, a short while after having quit, it will actually end the process. That however, is followed with an application error (Event 1000) visible in Event Viewer with the exception code 0xc0000005.

[Cyntonian]

Originally posted by JocularJosh:

Yeah same here, pretty much happens all the time I play it.
I either have to wait for it to close itself (it does so randomly after some time) or I actively have to close those taks via task-manager.

I do not get the application error though, that's weird.

The application error is only visible in event viewer. I validated with some friends and they all also have it unless they manually stop the process first.

[Countersync]

Some quick search shows:

Event ID 1000 (Application Error On Shudown)

While it seems '0xc0000005 caused an Access Violation' is similar to a segfault (Linux term) or out of process memory access.

It doesn't sound like this happens during normal play. Can you describe the setup for triggering the issue in greater detail? Like, you're trying to host a multiplayer game off of your PC but not interacting with the application? What state do you leave things in? My own two temporary methods for releasing the mouse lock are opening an inventory or hitting J to bring up the Journal.

[Cyntonian]

Originally posted by Countersync:

Some quick search shows:

Event ID 1000 (Application Error On Shudown)

While it seems '0xc0000005 caused an Access Violation' is similar to a segfault (Linux term) or out of process memory access.

It doesn't sound like this happens during normal play. Can you describe the setup for triggering the issue in greater detail? Like, you're trying to host a multiplayer game off of your PC but not interacting with the application? What state do you leave things in? My own two temporary methods for releasing the mouse lock are opening an inventory or hitting J to bring up the Journal.

To clarify, this is after quitting the game. It's NOT alt-tabbing and then it crashes in the background. The game is quit via main menu, but the process is still running until shortly after it shuts down and logs the application error event in event viewer.

[MechWarden]

Originally posted by Cyntonian:

Originally posted by JocularJosh:

Yeah same here, pretty much happens all the time I play it.
I either have to wait for it to close itself (it does so randomly after some time) or I actively have to close those taks via task-manager.

I do not get the application error though, that's weird.

The application error is only visible in event viewer. I validated with some friends and they all also have it unless they manually stop the process first.

I need to check that out. Didn't dawn on me to even check the Event Viewer.

I always thought it was doing some sort of debugging stuff at the end.

It is a common problem for it to keep running after a supposed graceful exit. If it isn't exiting out properly, the devs need to know and should fix it.

[Carnage]

Have the same issue, You can check Reliability Monitor (enter in Windows search). It shows that Abiotic Factor "Stopped working" after every proper exit.

[Kenshi]

Same issue here

[MechWarden]

When poking at the game to check on other things it dawned on me to check this, and sure enough I have errors for each time I closed the game.

Going to submit a bug report on this, since that feels like something that needs to be addressed. It shouldn't habitually exit ungracefully and it shouldn't take that long for it to close.

Edit:
Just noticed, it didn't happen if I opened the game and closed it without running a save.
2nd Edit:
Nor simply opening up the save and quitting soon after. There must be something going on in the game, during regular gameplay, that makes the game hang while exiting.
3rd Edit:
Seems to be related to a file call "ntdll.dll", which apparently seems to be a known problem for a couples years now.

[joshballz]

I don't mean to necro an old thread, but this is the only one I've found and I'm getting the same error. Has anyone been able to figure out why?

[MechWarden]

Nope.
This is still a persistent issue.

It seems harmless, and I know I submitted a bug report, but it still happens after playing the game some short amount of time.

[Caramel_Clown]

I've had it few times. All I did was press the button to stop the application in steam and it closes. Doesn't seem to cause any issues otherwise.

[joshballz]

Thanks for the replies. I agree, it seems mostly harmless. I'm just paranoid from a past experience with random errors.

[CombatWombat]

Originally posted by Caramel_Clown:

I've had it few times. All I did was press the button to stop the application in steam and it closes. Doesn't seem to cause any issues otherwise.

This works for me too. Also killing it in the task manger seems to work with no downsides. I do it quite often.

[david_bs]

Just to keep this fairly current, it seems I've had this happen after the last? patch. Didn't have the problem before.

[MechWarden]

This has happened as far as I can remember. I'm wanting to say it happened with Playtest 2 and the Demo, but I'll stick with it happening since it was released in Early Access.