crwdns2933423:0crwdne2933423:0
crwdns2918538:0crwdne2918538:0

crwdns2934243:0crwdne2934243:0 Sam Goldheart crwdns2934247:0crwdne2934247:0

crwdns2934249:0crwdne2934249:0:

The problem seems to go away if you decide to turn off “Displays have separate Spaces” from System Preferences —-> Mission Control. Of course, this means you don’t really have two separate split screens. However, it seems this is the reason why the WindowServer goes nuts in terms of CPU utilization. Seems like an OS-level issue, not really a hardware problem.

crwdns2915684:0crwdne2915684:0:

-deleted
+open

crwdns2934245:0crwdne2934245:0 iRobot

crwdns2934249:0crwdne2934249:0:

The problem seems to go away if you decide to turn off “Displays have separate Spaces” from System Preferences —-> Mission Control. Of course, this means you don’t really have two separate split screens. However, it seems this is the reason why the WindowServer goes nuts in terms of CPU utilization. Seems like an OS-level issue, not really a hardware problem.

crwdns2915684:0crwdne2915684:0:

-open
+deleted

crwdns2934241:0crwdne2934241:0 Srinivas Murty

crwdns2934249:0crwdne2934249:0:

The problem seems to go away if you decide to turn off “Displays have separate Spaces” from System Preferences —-> Mission Control. Of course, this means you don’t really have two separate split screens. However, it seems this is the reason why the WindowServer goes nuts in terms of CPU utilization. Seems like an OS-level issue, not really a hardware problem.

crwdns2915684:0crwdne2915684:0:

open