UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.75 Safari/537.36

Steps to reproduce the problem:
1. Start dwm as window manager.
2. Hide chrome (via window set selection).
3. Have chrome bring up an alert().

What is the expected behavior?
Something reasonable.

What went wrong?
Chrome continuously fights with dwm about whether it is visible, to the point where it acquires a *massive* backlog of CPU work and becomes *unusable* even when made visible.

Did this work before? N/A 

Chrome version: 50.0.2661.75  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 21.0 r0