Process lingers and uses quite a bit of resources #3016
Comments
|
The UI closes immediately but the process has to clean up after self and do things like write the preferences to disk so this is as expected and not something to be fixed. I don't understand what you are looking for as a solution here or why this is a problem. |
|
this is a huge problem, because faf-client.exe can hang while taking 40% of 10 core cpu and being at very high power usage for a long time. I'm talking lilke 10+ minutes. It's definitely not just writing game prefs to disk. It also means that you can't restart the client without killing this process through task manager first. It's like this for 2+ months already. IT also starts eating more and more CPU and more and more power even before you close the UI. At some point, the client becomes unusable |
|
Just to clarify, the process exists for 10+ minutes after you closed the ui? |
|
Do you have a client.log from when it takes 10+ minutes? |
I understand that it needs to finish up a task or two, but using so much system resources for such a long duration (several minutes) feels like a bit much. I tried to find a log for you, but it didn't write it after killing the process 😄 . The logs are quite large (10MBs+ worth of disk storage) |
|
I'm on windows 10. The process sometimes closes after a minute or so, and some times just hangs in there until I kill it. Not sure which logs would be useful, but here's some big one. It's from yesterday, and yesterday it happened multiple times. faf client was already idling at 40% cpu and high power usage even before I killed it, so maybe there's something in the log |
|
Linux: 400% CPU usage 2gig ram usage. Longer the client has been running, higher the probability that it does not close right. Bad behavior starts when pressing the closing X and CPU usage shoots up. Almost as if some threads gets into infinite loop, where there is no work but exit condition is not met. If I start and close the FAF instantly, it closes as expected. Update: Happened today again, let it run and it finally closed after ~30 seconds. I always terminated it much sooner. When the client closed, computer time was 15:47 Last lines on client.log: |
|
Same thing. If it runs for more than an hour it's pretty much impossible for faf-client process to reliably exit. Performance also degrades the longer it stays open, so I suspect there might be memory leaks as well |
|
Same for me. As a side effect the process staying open for a long time after the client closes means that you can't quickly restart it w/o using the task manager to kill it manually. Otherwise pressing the faf client exe just does nothing. Possibly related to this and/or #3012: If I close the client after it being open for a couple of hours, it happens semi-reliably that, like 5 minutes after closing it, I hear the distinct "message received" sound from the client, after which the process is also gone from the task manager. |
|
There is no errors in the logs that would cause a long open time. Does the client use high resources during runtime? |
|
Yes for me, the longer it runs the more it eats. Also, the performance degrades drastically over time. |
|
Can you give more information on your system as I am unable to replicate it as when I run it locally for stress tests over a week it remains at a stabe resource usage. Can you also describe what actions you normally take with like the interactions. |
|
faf client runs on windows 10. It's installed on SSD. CPU is intel core i9-9900k, gpu is radeon 7900xtx, although it also happened on my previous gpu, which were nvidia 1070gtx. Overall, it seems like the more actions you do with the client, the faster it slows down. When I just open the client, after it logged me in, I'd see this situation: After clicking around, just like randomly between tabs, maybe loading my replays list, RAM usage gradually gets up but doesn't seem to ever go down. |
|
What build of windows 10 are you using? |
|
Edition Windows 10 Pro |
|
A (or three) thread dump(s) would help to diagnose the issue. You should be able to get them using jattach. |
|
Do I just attach with jattach during the normal flow and then close the client? I assume I attach to faf-client.exe, right? |
|
@valignatev sorry for the late reply.
|
|
Hey no problem. But actually since one of the recent updates I don't have this issue as bad anymore. Now, faf-client.exe would just chill for 5-ish seconds after the client is closed and then exit successfully. I also don't have the accumulated lag anymore, so don't have to restart the client all the time. But I'll do the threaddump if this ever comes back |
|
I think I found the issue. The Chat service tried to reconnect after the connection was closed always XD |
|
Actually, it makes sense! Right after i posted my previous message I had a situation where chat disconnected in the client and I've tried to restart the whole program to reconnect again (because trying to reconnect to the chat from the client never worked for me for some reason). And faf-client.exe stuck again for like a solid minute. But then I restarted the client again in hopes that the bug came back and I can threaddump it, but it was fine haha |
Describe the bug
The process lingers after exiting for quite a while and consumes quite a bit of resources:
To Reproduce
Start the application, let it stay in for a few hours and exit it.
OS
Windows
The text was updated successfully, but these errors were encountered: