New issue
Advanced search Search tips

Issue 643342 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chromium is slowly / does not respond on dualmonitor with different virtual desktops

Reported by chris.re...@gmail.com, Sep 1 2016

Issue description

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

Steps to reproduce the problem:
1. Run a Window-Tilingmanager like DWM
2. Run chromium on 2 monitors
3. Have 2 chromium instances open on both screens
4. Change on one screen the virtual desktop (workspace)
5. The active chromium on the other screen will not act very slowly and will not respond to user interaction, HTML5 videos on youtube or other services will be stucked (sound is no problem)

What is the expected behavior?
chromium should behave normally and respond to user input as fast as like I have just 1 chromium instance open.

What went wrong?
the active chromium instance will respond slowly, HTML5 videos will be stucked.

Did this work before? N/A 

Chrome version: 52.0.2743.116  Channel: n/a
OS Version: 4.7.2-1
Flash Version: No flash installed

While trying to trace this issue.. I get an 'Aw, Snap!' page on the stucked chromium. Maybe because the buffer was already full? I stopped the first time at 100%.. then I got the snap page.. at the second try it has worked with just 46% buffer usage.
 
vid-2016-09-01-212845.mp4
2.1 MB View Download
trace.gz
6.7 MB Download
Sorry I have a mistake in the last comment..
It should be:

"The active chromium on the other screen will act very slowly and will not respond to user interaction, HTML5 videos on youtube or other services will be stucked (sound is no problem)"
Project Member

Comment 2 by sheriffbot@chromium.org, Sep 4 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment