8k displays black out (media report) |
||
Issue descriptionhttps://www.theverge.com/2017/9/12/16293326/dell-8k-monitor-review-ultrasharp-up3218k has the following text: "The other problem, I found, is that most software isn’t yet ready for or properly tested to run at such an insane resolution. "Chrome on Windows was the biggest culprit for me. The Dell monitor would sometimes black out the entire browser page I was trying to look at, or, even more annoyingly, it would flicker on pages with constantly refreshing content such as Chartbeat. Opening up my library in Google Photos was fine, but as soon as I tried to edit a picture, the browser would freak out and start doing weird stuff like zooming way in on one corner of the image. My testing rig is built around an Nvidia Titan X, Intel Core i7-6950X, and 64GB of RAM (because why not?), and I’ve had no such performance issues with any other displays linked up to it." Assigning to a media peep + a Windows peep. I trust that you two will know how to diagnose/assign it further.
,
Sep 12 2017
Nope, sadly. However, I am almost 100% sure that this is the same as bug 695427. I think we need to do something smarter with regards to our memory limits - Vlad's change on that bug doubles the limit for 4K monitors, and we'll likely need to raise it further for 8k.
,
Sep 12 2017
+1 to this looking like the same bug. And +1 to the idea on the other bug that we should put in an adaptive system so that our texture memory limits scale in proportion to monitor pixels. We'll have to quadruple them for 8K. I wonder how well we handle multi-mon?
,
Sep 12 2017
Re multimon - The limits are per-renderer, not overall, so for multimon we only have a problem if you stretch a single window across both monitors. Having two windows on two monitors shouldn't be impacted.
,
Sep 13 2017
Well, don't forget that a render process can run multiple visible tabs. (Control-clicking on links to open them in new tabs yields both tabs in the same render process.) I don't know if that affects your answer to Bruce's question in comment 3. (And c'mon, I'm trying to give you an excuse to go shopping here :) ) |
||
►
Sign in to add a comment |
||
Comment 1 by kbr@chromium.org
, Sep 12 2017Components: Internals>GPU>Internals