4 ms·

> hangs from the the max-texture-size-equivalent tes I reported this bug back in 2015 and they have made no progress on it. It seems Nouveau just doesn't have

by slacka 8y ago

> hangs from the the max-texture-size-equivalent tes I reported this bug back in 2015 and they have made no progress on it. It seems Nouveau just doesn't have the resources or man power. I can't really blame Google here. You don't want the browser to be able to hard lock system(not even a Magic SysRq will reboot it) [1] https://bugs.freedesktop.org/show_bug.cgi?id=92136 https://bugs.freedesktop.org/show_bug.cgi?id=92136

lucb1e 8y ago
> You don't want the browser to be able to hard lock system(not even a Magic SysRq will reboot it) Wait, this isn't just rendering bugs a la "some WebGL things will show green instead of red", it kills your system entirely? I thought the only effect this blacklisting had was making WebGL unavailable for everyone instead of buggy for a small minority. This just flipped my opinion. Related, this might also explain the strange bluescreen bug my girlfriend had with Windows 8 + Firefox on her laptop. She switched to Google Chrome a few years ago because every time she used Firefox, her laptop would bluescreen within a few hours (either while Firefox was still running, or at some point later). I didn't know bugs outside of the OS could still do that kind of thing (I thought they started squashing such bugs with Windows 95 and finished somewhere around Vista) and wrote the Firefox thing off as triggering some extremely obscure Windows OS-level issue. Maybe I should check if there is a driver blacklisted by Chrome, though it seems more likely Chrome just doesn't happen to trigger it (like all other software running on it, it really is only Firefox).
- Wowfunhappy 8y ago
  Driver crashes can easily take down a system. That's why driver quality matters so much. This is true on every OS. (Although, Windows 7+ has mechanisms to help recover from GPU driver crashes specifically, which usually work.) Also, Chrome can render WebGL on the CPU. It's slower but will still work.

by slacka 8y ago

lucb1e 8y ago

> You don't want the browser to be able to hard lock system(not even a Magic SysRq will reboot it) Wait, this isn't just rendering bugs a la "some WebGL things will show green instead of red", it kills your system entirely? I thought the only effect this blacklisting had was making WebGL unavailable for everyone instead of buggy for a small minority. This just flipped my opinion. Related, this might also explain the strange bluescreen bug my girlfriend had with Windows 8 + Firefox on her laptop. She switched to Google Chrome a few years ago because every time she used Firefox, her laptop would bluescreen within a few hours (either while Firefox was still running, or at some point later). I didn't know bugs outside of the OS could still do that kind of thing (I thought they started squashing such bugs with Windows 95 and finished somewhere around Vista) and wrote the Firefox thing off as triggering some extremely obscure Windows OS-level issue. Maybe I should check if there is a driver blacklisted by Chrome, though it seems more likely Chrome just doesn't happen to trigger it (like all other software running on it, it really is only Firefox).

Wowfunhappy 8y ago
Driver crashes can easily take down a system. That's why driver quality matters so much. This is true on every OS. (Although, Windows 7+ has mechanisms to help recover from GPU driver crashes specifically, which usually work.) Also, Chrome can render WebGL on the CPU. It's slower but will still work.