Takes forever to quit running

[rzn6jw]

Does anyone else have the issue where you quit TLOU and it takes about a minute for the game to actually quit running, even after you get to your desktop?

[breadman]

might be syncing cloud saves

[rzn6jw]

Could be but it shouldn't take that long. Hogwarts and Jedi do the same thing.

[kgkong]

What CPU and RAM do you have?
Probably a slow issue with your system ending processes and running any cloud syncing.

[rzn6jw]

Ryzen 9 5950X, 64Gb DDR4 3200 ram and ASUS RTX 4070 Super OC.

[Inflames]

Originally posted by KingGorillaKong:

What CPU and RAM do you have?
Probably a slow issue with your system ending processes and running any cloud syncing.

its the game not our system the problem...

[kgkong]

Originally posted by Inflames:

Originally posted by KingGorillaKong:

What CPU and RAM do you have?
Probably a slow issue with your system ending processes and running any cloud syncing.

its the game not our system the problem...

You'd be surprised. The only times I get stuck with a game not quitting is from a system side issue. More or less it's usually just an issue with the cloud sync but it's not always that. Sometimes the game quits and the CPU hangs because of what's going on in the background. Sometimes the game hangs when I quit because instead of exiting properly I use ALT+F4. Sometimes there's been a handful of memory leaks from various games and software I run and this just slows down the system and screws with Windows properly ending the process.

[kgkong]

Originally posted by rzn6jw:

Ryzen 9 5950X, 64Gb DDR4 3200 ram and ASUS RTX 4070 Super OC.

Are you using ALT+F4 to exit?
When was the last time your modem was power cycled/restarted?
How much memory is currently being used on your system? Out of your 64GB memory how much does Windows say is currently used?

[Salvation]

The game doesn't quit properly. It crashes after you quit to desktop and creates a "TLOU has crashed" error in Reliability History. This was introduced with one of the patches, as it wasn't like this during the first few versions of the game in April or so.

I always quit to desktop and end up having to end the process through Task Manager to get it to ♥♥♥♥ off thoroughly.

[1% Aoukar]

why is it a problem if the game takes 1 min to close?

[kgkong]

Originally posted by IneptiArk:

why is it a problem if the game takes 1 min to close?

Because it's unnecessarily using system resources and in some instances can impact shutting down or restarting your PC because a process is still actively running.

Had this issue not too long ago with another game, and in a mix of the known issues with game crashes and me using ALT+F4 to close the game, not every process closed and the game was stuck running in the background. I closed the process in Task Manager and there was another process still running in the background that had not been killed (or if associated with the game was not told the game was killed) and it hung. Closed every running app, force quit a bunch of stuff in Task Manager, still wouldn't close the game. Trying to exit Steam didn't work. Force quitting Steam still didn't work cause after I did that, I tried to restart my PC and Windows said that the game was still running and it could not shutdown, please wait for the app to finish closing.

All in all it took about 5 minutes to get my PC restarted when it should have only taken 40 seconds.

[CJM]

The worst offender for me has been the Master Chief Collection's Halo: Combat Evolved with the Anniversary graphics enabled.

The Halo:CE memory leak is substantial, and if I play for an hour my system becomes mostly unresponsive while the game takes 5 minutes to cleanup the memory and exit properly. All I can do is watch the memory allocation go down until the application exits, and the memory does not seem to be freed entirely until the application fully exits.

TLOU's process takes time to exit, but compared to Halo:CE it is no where near "forever".

[kgkong]

Originally posted by CJM:

The worst offender for me has been the Master Chief Collection's Halo: Combat Evolved with the Anniversary graphics enabled.

The Halo:CE memory leak is substantial, and if I play for an hour my system becomes mostly unresponsive while the game takes 5 minutes to cleanup the memory and exit properly. All I can do is watch the memory allocation go down until the application exits, and the memory does not seem to be freed entirely until the application fully exits.

TLOU's process takes time to exit, but compared to Halo:CE it is no where near "forever".

Wow, pretty sad that 343 could only fix the memory leak that way rather than stopping them from even being a problem in the first place.

[rzn6jw]

It could be that the game is clearing memory. If I go to the desktop after quitting the game, I can see the memory used slooowwwly going from 29G back to 9G. Seems that, in this day and age, clearing memory should be almost instantaneous.

[episoder]

no issues on my end. whether i alt+f4 or quit to desktop. if there are memory issues you should get a memory cleaning utility. it's a undocumented fact that windows is a sloppy software not cleaning up discarded memory. i use "emptystandbylist" to do that. set as a scheduled task that runs every 5 minutes. you can find tutorials via google.

[CJM]

Originally posted by KingGorillaKong:

Originally posted by CJM:

The Halo:CE memory leak is substantial, and if I play for an hour my system becomes mostly unresponsive while the game takes 5 minutes to cleanup the memory and exit properly.

Wow, pretty sad that 343 could only fix the memory leak that way rather than stopping them from even being a problem in the first place.

They haven't fixed the memory leak.

You play the game for an hour, then you get 20 FPS averages as it exceeds 32GB of RAM and hits the page file. So you exit the game and wait an absurdly long time for the computer to become the least bit functional.