You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hi! Using MediaMate for a while now and I just noticed that after some time it uses around 25-30% cpu and it cranks up the WindowServer process to about 50-60% CPU usage. When I force quit the app WindowServer goes back down to about 10% CPU. Reopening MediaMate fixes the issue for some time but it will come back after all.
To Reproduce (actually I'm just writing what I do before this happens I don't know whether everything is in connection with the issue)
Event controller mode: Lunar
Style: notch
Play some music from YouTube using Safari for about 3-4 hours.
It's sunny here so the brightness changes a lot.
Expected behavior
It won't consume that much after some time.
Please complete the following information:
OS: Sonoma 14.6.1
Device: 2021 14" M1 pro
Version 3.6.1 build 283
Additional context
Sometimes it happens after 3-4 hours but sometimes it takes 1-2 days to consume high CPU.
The text was updated successfully, but these errors were encountered:
Thank you for the bug report. I will try to reproduce this issue. When MediaMate is inactive (no HUDs are shown), all its windows are removed, so I'm surprised about the CPU usage of WindowServer.
Describe the bug
Hi! Using MediaMate for a while now and I just noticed that after some time it uses around 25-30% cpu and it cranks up the WindowServer process to about 50-60% CPU usage. When I force quit the app WindowServer goes back down to about 10% CPU. Reopening MediaMate fixes the issue for some time but it will come back after all.
To Reproduce (actually I'm just writing what I do before this happens I don't know whether everything is in connection with the issue)
Expected behavior
It won't consume that much after some time.
Please complete the following information:
Additional context
Sometimes it happens after 3-4 hours but sometimes it takes 1-2 days to consume high CPU.
The text was updated successfully, but these errors were encountered: