Steam client version (build number or date): Aug 1 2018, at 22:27:11
Distribution (e.g. Ubuntu): Kubuntu 17.10
Opted into Steam client beta?: [Yes/No] Yes (steam-runtime-beta-release_2018-06-14)
Have you checked for system updates?: [Yes/No] Yes
Please describe your issue in as much detail as possible:
When running CSGO with new Panorama UI system resource usage is quite high, so even on first map I'm hitting swap (6G+2G in system, nothing else running, even stopped unused services) and CPU is topping out one core all the time (different cores) running at average of just under 200%. It's AMDGPU, AMD A8-7600 Radeon R7, 10 Compute Cores 4C+6G.
As soon as a second map is loaded then the system hangs. It doesn't crash or lock, and alt-f4 will eventually get answered or I can SSH in and kill the client but it takes a few minutes just for the login to be handled.
I tested on Dust2 for about 1 hour and resources had risen a little but was running fine, FPS is about 40-48 (8-10 average above the previous UI). Ending that game and starting a new map then causes the hang a little while after the map loads.
Running with -scaleform in load options works fine. Load average then is about 100-110%, memory use appears to be 1.5-2G less.
I took some pmap's which might help, I don't really know. There are more errors in the stdout but nothing that looks like a definite cause, TBH it looks most like a memory leak to me, that the client is failing to release memory used for former maps. When combined with higher resource usage it's hanging.
Happy to do tests or provide logs on request. I reported to support and they said to register it here.
Your system information
Please describe your issue in as much detail as possible:
When running CSGO with new Panorama UI system resource usage is quite high, so even on first map I'm hitting swap (6G+2G in system, nothing else running, even stopped unused services) and CPU is topping out one core all the time (different cores) running at average of just under 200%. It's AMDGPU, AMD A8-7600 Radeon R7, 10 Compute Cores 4C+6G.
As soon as a second map is loaded then the system hangs. It doesn't crash or lock, and alt-f4 will eventually get answered or I can SSH in and kill the client but it takes a few minutes just for the login to be handled.
I tested on Dust2 for about 1 hour and resources had risen a little but was running fine, FPS is about 40-48 (8-10 average above the previous UI). Ending that game and starting a new map then causes the hang a little while after the map loads.
Running with -scaleform in load options works fine. Load average then is about 100-110%, memory use appears to be 1.5-2G less.
I took some pmap's which might help, I don't really know. There are more errors in the stdout but nothing that looks like a definite cause, TBH it looks most like a memory leak to me, that the client is failing to release memory used for former maps. When combined with higher resource usage it's hanging.
Happy to do tests or provide logs on request. I reported to support and they said to register it here.
Steps for reproducing this issue: