Dismiss Notice
This Section is READ ONLY - All Posts Are Archived

[Known] Client keeps running in the background after quitting

Discussion in 'Release 43 Bug Forum' started by that_shawn_guy, Jun 29, 2017.

Thread Status:
Not open for further replies.
  1. that_shawn_guy

    that_shawn_guy Bug Hunter

    Messages:
    1,414
    Likes Received:
    3,748
    Trophy Points:
    125
    Location:
    earth... mostly
    06/29/2017 16:45
    Title:
    Reproduction Rate:
    Blocker?
    Details: After quitting (waiting 20 seconds to quit or not) the client UI closes, but the process is still running in the background. I have to force quit the process to get it to die.
    Steps to Reproduce: Launch from non-steam launcher, login, play, quit.
    User Specs:
    OS: Mac OS X 10.12.5
    CPU: Intel(R) Core(TM) i7-6920HQ CPU @ 2.90GHz (8) System RAM: 16384
    GPU: AMD Radeon Pro 460 OpenGL Engine GPU RAM: 4096
    SotA.EarlyAccess.LIVE.OSX.64.616.Date.06.28.17
    Area: POT_forest_metropolis_02_template/Crossroads
    Area Display Name: Crossroads
    Loc: (75.9, 36.0, -273.3)
     
    Spartus likes this.
  2. Pebbles

    Pebbles Avatar

    Messages:
    107
    Likes Received:
    227
    Trophy Points:
    18
    Gender:
    Female
    Location:
    Stocking my vendors
    Also happening to me last about 50% of the time last release and 100% of the time this release. I am on Mac also, but a different version of OS X.

    OS: Mac OS X 10.11.6
    CPU: Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz (12) System RAM: 65536
    GPU: AMD Radeon HD - FirePro D500 OpenGL Engine GPU RAM: 3072
     
  3. Spartus

    Spartus Avatar

    Messages:
    80
    Likes Received:
    184
    Trophy Points:
    8
    Gender:
    Male
    Location:
    St. Louis, Missouri
    This also occurs for me on R43 when quitting the Linux client, but my client UI doesn't even close, it just hangs the entire OS with continuous hard drive activity (as if swapping memory). I can't even open another console to kill the process, so I have to hard reset.

    SotA.EarlyAccess.Linux.64.617.Date.06.29.17
    OS: Ubuntu Gnome 17.04
    CPU: Intel Core i3 540, 8 GB RAM
    GPU: Nvidia GTX 750 Ti
     
  4. Almar

    Almar Avatar

    Messages:
    281
    Likes Received:
    689
    Trophy Points:
    40
    Gender:
    Male
    Location:
    Northern Ireland
    Same here - on WIN 10 PC though

    7 times out of 10 I have to force end/ crash logout.
     
  5. Lexie

    Lexie Bear Queen Emeritus

    Messages:
    842
    Likes Received:
    2,902
    Trophy Points:
    93
    I've created a bug for this so we can investigate further. Bug #: 47769. Thank you.
     
    Spartus likes this.
  6. Wintermute of CoF

    Wintermute of CoF Avatar

    Messages:
    1,372
    Likes Received:
    2,432
    Trophy Points:
    113
    Gender:
    Male
    Location:
    London, United Kingdom
    I've seen similar on Linux, though I've always been able to kill the client from a console. Remember that you can switch to a different TTY with Ctrl + Alt + function key, that might work better than trying to get at a terminal in the same X session as the game.

    Also if you did anything in game which launched another process (e.g. typed /bug or clicked on a link which caused a browser window to open) try closing out that other process (e.g. the browser) before quitting the game.
     
    Spartus likes this.
  7. Alley Oop

    Alley Oop Bug Hunter Bug Moderator

    Messages:
    15,728
    Likes Received:
    19,493
    Trophy Points:
    153
    it might not even need a seperate tty: i have a keyboard shorcut for xkill.
     
    Spartus likes this.
  8. Spartus

    Spartus Avatar

    Messages:
    80
    Likes Received:
    184
    Trophy Points:
    8
    Gender:
    Male
    Location:
    St. Louis, Missouri
    Yes, I tried that but my PC was so busy it wouldn't respond, sometimes it works, sometimes not. The only times in my personal experience that I've seen the virtual console/TTY not respond is when the OS runs out of memory, coupled with a slow CPU. It's possible that it would respond if I waited long enough (but then one often get cases where the login times out before they can type in the password...) Anyway, I experimented again, running into Central Brittany and Brittany Estates and then hitting Novia (and watched the CPU/memory usage using top, and my CPU is usually pegged between 150 to 200 % (my dual core i3 540 is rather old) but it runs well enough. Then, when I quit the game, the hard drive activity went way up, but the CPU eventually dropped down under 50% utilization. The available swap memory then started tanking over several minutes and almost dropped under 20 megs, and then about 4 minutes later the UI closed, the process ended, and the available swap went back up to 7+ gigs. Whatever the client is doing after you click Quit, who knows, but it is very memory intensive.
     
    Wintermute of CoF likes this.
  9. Ataniiq

    Ataniiq Avatar

    Messages:
    82
    Likes Received:
    90
    Trophy Points:
    8
    This is also plaguing my system.
     
Thread Status:
Not open for further replies.