Issue metadata
Sign in to add a comment
|
Chrome stalls when opening tab in backgrounded window |
||||||||||||||||||||||||
Issue descriptionWhere I'm seeing this: - I have two Chrome windows and the hangouts extension open. - One of the normal Chrome windows is completely behind the other (via a tabbed layout in XMonad, which hopefully is irrelevant). - When I click a link in hangouts, it opens in the window in the background, but doesn't actually load. Chrome appears to completely freeze until I foreground the window opening the new link. Trace here (https://drive.google.com/a/google.com/file/d/0BxE9dpLjlZbPVXpyV2NJSTVfUkk/view?usp=sharing) - Googlers only. This is probably either a scheduling bug or a UI issue. I'm leaning towards thinking it's a UI issue, based on the trace. Looks like Widget::Show is synchronous, and somehow ends up blocking on me switching the backgrounded window into the foreground.
,
Jan 26 2017
This sounds like it has the same root cause as bug 505669 . I think the UI thread is blocking on receiving a MapNotify, which it won't get because xmonad doesn't map the window until it's visible. This CL should fix it: https://codereview.chromium.org/2329323002/ But for some reason the author stopped working on it
,
Jan 26 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sadrul@chromium.org
, Jan 26 2017