Comment #3 on issue 29723 by jonmpryor: Failing searches minimize other windows. http://code.google.com/p/chromium/issues/detail?id=29723
Well, now I know why the windows flicker and things are generally fubar. Metacity is dying. Seriously. Find the current pid: ps aux | grep metacity: jon 15196 0.7 0.4 346772 15264 ? Sl 10:06 0:00 /usr/bin/metacity Search for non-existant text, then re-run the above ps command: jon 15436 1.1 0.4 346764 15240 ? Sl 10:15 0:00 /usr/bin/metacity Different pid, ergo different process. Now *why* is metacity dying? So obviously the bug, per se, isn't in Chrome (metacity shouldn't be dying!), but the problem is caused -- reliably! -- by Chrome (and no other app). So it's gone from a "please fix the Chrome bug" to a "please workaround the metacity bug". Still wondering how to further diagnose this... -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
