![]() ![]() If there is anything else I can do to try and get more info let me know, happy to help. My two machines (i7-10th gen and ryzen 3700x) both exhibit similar behavior. ![]() I tried to open up the dev tools to try and get a profile, but the entire window becomes non-responsive when the behavior starts.Īll of our Debian based users are seeing this on the desktop client. To the point that if I can type, there is a delay of a few seconds between when I press a key and when it is rendered. When the first process has the CPU and is pinning it, the mattermost UI becomes extremely sluggish or outright non-responsive. ![]() ![]() exhibit what looks like a pretty standard GC sweep (significant CPU usage across all cores and a dramatic drop in resident memory), this lasts less than a second. Once the mattermost-desktop -enable-crashpad process lets go of the CPU I see the process with args mattermost-desktop -type=renderer -enable-crashpad -enable-crashreporter. In the fact the file will be so stupidly large that you're better off running a tail -250 /cpu.txt instead. Memory usage on that process does not climb appreciably. top -b > /cpu.txt Then when your PC freezes, simply open the (probably huge) text file and check the last entry for some detail on what was running just before the crash. ps -eo pcpu,pid,user,args sort -r -k1 less Also, you can write a small script in bash or perl to read /proc/stat and calculate the CPU usage. using top : This will show you the cpu stats top -b -n 1 grep Cpu using ps: This will show you the cpu usage for each process. When i switch contexts the process with args: mattermost-desktop -enable-crashpad goes to 100% CPU usage for about 3-5s. You can use top or ps commands to check the CPU usage. The easiest way to cause this is just switching back and forth between teams.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |