When reloading the library memory to RAM, a code signing check is done and fails, causing a WindowServer crash.
Drawing is suprisingly CPU intensive, easily 30-50% CPU.
That tallies up well with other forum comments elsewhere. I noticed that after a few hours, WindowServer would be consuming 3GB+ of memory, with a few GB compressed. If it occurs when you connect an external monitor to your Mac, change the screen resolution, or play around with transparency effects, the good news is that you aren’t dealing with a virus. Almost always half or more 4+gb is allocated to WindowServer. High memory usage WindowServer (5GB.) Close. Targus Validates DisplayLink Manager Release 1.3 for Big Sur, Catalina, and M1 MacBooks.
