| ▲ | OGEnthusiast 10 hours ago |
| FWIW haven't experienced this at all on an M4 Max (with Slack and VSCode open). |
|
| ▲ | Etheryte 10 hours ago | parent | next [-] |
| To be fair, the M4 Max is such a beefy machine that you could do a lot of things wrong and still not notice it. |
| |
| ▲ | OGEnthusiast 10 hours ago | parent [-] | | True, but looking at Activity Monitor I don't see any CPU or GPU spike when having an Electron app open and scrolling in Chrome (vs scrolling without any Electron apps open) | | |
| ▲ | masklinn 9 hours ago | parent | next [-] | | Apparently the issue has to do with transparencies (shadows and straight up transparency), so could be a question of capabilities not capacity e.g. older gens have less range and some non-default require falling back to software whereas newer gens can keep to hardware. | |
| ▲ | STRML 10 hours ago | parent | prev [-] | | Watch your power usage. With large windowed VSCode or Cursor, you will see far higher CPU and GPU usage by WindowServer and more system power consumption. It’s easier if you track it with stats.app. |
|
|
|
| ▲ | bdash 8 hours ago | parent | prev [-] |
| Strangely the WindowServer issue is a constant issue on my personal MacBook Pro, but I've never seen it on my identical work MacBook Pro. It seems like there's some other factor that is necessary to trigger the problem. |
