Jump to content
Dante Unbound: Known Issues ×
Dante Unbound: Share Bug Reports and Feedback Here! ×

Steam version of Warframe has trouble actually closing, holding onto more than 4 gb of RAM


TARINunit9
 Share

Recommended Posts

After exiting out of Warfarme, the application doesn't actually close. My Steam friends list still lists me as being in-game, and Task Manager confirms the Warframe application is still using its allocated 4.6 gb of system memory.

As a test, I opened a YouTube video in the Steam Web Browser and left the audio for it on, then used Warframe's in-game "close the game" button. The audio for the video was still running five minutes later until I eventually just force-quit Warframe from Task Manager

  • Like 2
Link to comment
Share on other sites

This happens sometimes when it's running closing routines - could you possibly take a look at the EE.log immediately after the session (in '%LOCALAPPDATA%/Warframe' directory) and see if it's stuck on anything in particular?

Otherwise, this might be some weird issue with how Steam's new overlay changes interact with playing content and closing games, but I don't ever use the overlay web browser so I can't say. I just know that I've had this issue maybe once or twice the past few years and a restart usually prevents it from occurring again.

Link to comment
Share on other sites

14 hours ago, Naroxas44 said:

This happens sometimes when it's running closing routines - could you possibly take a look at the EE.log immediately after the session (in '%LOCALAPPDATA%/Warframe' directory) and see if it's stuck on anything in particular?

I have the data, should I post it here or no?

I should mention that it took Warframe a good six minutes to go from "window closed" to "Steam recognizes I'm not in game" but it did eventually do so without Task Manager this time

Link to comment
Share on other sites

36 minutes ago, TARINunit9 said:

I have the data, should I post it here or no?

You could post redacted excerpts if you'd like, but the entire log itself contains stuff like IPs and email address so I'd avoid that if possible.

The main thing I'd focus on are the closing routines, near where the EE log says "Exiting main loop" - they should have timestamps and logging about shutdown routines that occur after the game client has closed (like IRC, session callbacks, profile saving, thread cleanup, etc). Mine generally finishes within' about 10s or so, looking at my last log.

Link to comment
Share on other sites

18 minutes ago, Naroxas44 said:

You could post redacted excerpts if you'd like, but the entire log itself contains stuff like IPs and email address so I'd avoid that if possible.

Yeah I've already checked for that, thanks for looking out for me

And on the off-chance DE still wants to see it:

Quote


3947.168 Sys [Info]: FlashMgrImpl::Shutdown
3947.169 Input [Error]: InputMgrWin::Shutdown
3947.187 Gfx [Info]: Destroying Graphics Worker Thread
3948.773 Gfx [Info]: Dx11SwapChain::Shutdown
3949.095 Sys [Info]: WM_DISPLAYCHANGE, driver reset queued:0
3950.558 Snd [Info]: Shutting down XAudio2!
3953.778 Net [Info]: UDP socket closed on port 4955
3953.778 Sys [Info]: Client killed
3955.694 Sys [Info]: Discord Service has begun shut down.
3955.694 Sys [Info]: Discord Service has successfully shut down.
3955.694 Sys [Info]: ===[ Exiting main loop ]====================================================================================
3955.694 Net [Info]: MatchingService::DeleteSession
3955.695 Net [Info]: IRC out: QUIT :Logged out of game
3955.869 Net [Info]: DeleteSessionCallback(1, {"rewardSeed":REDACTED})
3955.869 Net [Info]: Deleted session
3955.869 Net [Info]: MatchingServiceWeb::LeavePlatformPartyDone
3955.870 Net [Info]: Joining Port-Forwarding Worker
3955.871 Sys [Info]: Main Shutdown Initiated.
3955.874 Sys [Info]: TypeMgr cleaned 7296 instances (254us) and unbuilt 908 types (2.74ms) in 254us
3955.890 Sys [Info]: Shutting down context... [Heap: 1,409,006,272/2,316,238,848 Footprint: 8,490,672,128 Handles: 1,454]
3955.890 Sys [Info]: Context shutdown complete [Heap: 1,409,006,016/2,316,238,848 Footprint: 8,490,672,128 Handles: 1,454]
3955.894 Sys [Info]: TypeMgr cleaned 4 instances (107us) and unbuilt 0 types (2.88ms) in 107us
3955.894 Sys [Info]: Server stopped...
3955.894 Sys [Info]: PlayerProfileCommon::SaveProfile()
3955.894 Sys [Info]: UploadChallengeProgress nothing changed, skipping upload
OnUploadChallengeProgressResults: mRecentSeasonChallengeCompletions=0, mSavingRecentSeasonChallengeCompletions=0
3955.897 Sys [Info]: Profile hash on write: CD36663BCC89F3809D82F9AA879207CF
3955.953 Sys [Info]: Redirecting package save to: C:\Users\REDACTED\EE.cfg
3956.315 Sys [Info]: Skipping SavePackage for /REDACTED/EE.cfg (no changes detected)
3956.316 Sys [Info]: Saved package: /REDACTED/EE.cfg
3956.318 Net [Info]: UDP socket closed on port 4950
3956.320 Sys [Info]: Used 1 shared assets (0 async, 1 sync)
3957.495 Phys [Info]: PhysX SDK shutdown.
3957.579 Phys [Info]: PhysX scene manager shutdown.
Sys [Info]: All smart pointers were destroyed!
4107.619 Sys [Info]: Main Shutdown Complete.

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...