Bug#599812: Chrome rendering of HTML5 elements such as canvas and video crash X with xserver-xorg-video-intel
The new version of xserver-xorg-video-intel which is 2:2.13.0-2
combined with edge Chrome:
Google Chrome 10.0.612.1 (Official Build 69289) dev
WebKit 534.15
V8 3.0.0.1
User Agent Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.15
(KHTML, like Gecko) Chrome/10.0.612.1 Safari/534.15
Command Line /opt/google/chrome/google-chrome --restore-last-session
--flag-switches-begin --disable-outdated-plugins --flag-switches-end
seems to solve this problem. I think we can call this closed.
On Wed, Oct 20, 2010 at 1:50 PM, Jonathan E. Magen <yonkeltron@gmail.com> wrote:
> So I've now got version 2:2.12.0+shadow-2 of xserver-xorg-video-intel
> installed. HTML5 still crashes X but it comes right back up again.
> This is can be reproduced. Using Chrome with the following info from
> about:version
>
>
> Google Chrome 8.0.552.5 (Official Build 62886) dev
> WebKit 534.10
> V8 2.4.9.1
> User Agent Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.10
> (KHTML, like Gecko) Chrome/8.0.552.5 Safari/534.10
> Command Line /opt/google/chrome/google-chrome --flag-switches-begin
> --disable-outdated-plugins --enable-tabbed-options --flag-switches-end
>
> This still happens and the bug still exists in the new version.
>
> On Mon, Oct 11, 2010 at 6:01 PM, Cesare Leonardi <celeonar@gmail.com> wrote:
>> On 10/11/2010 03:43 PM, Jonathan E. Magen wrote:
>>>
>>> Package: xserver-xorg-video-intel
>>> Version: 2:2.9.1-4
>>> Severity: important
>>>
>>> When using the Chrome 7 preview release, rendering pages with
>>> advanced HTML5 effects such as<canvas> and<video> will cause X to
>>> crash with the xserver-xorg-video-intel driver. I suspect this might
>>> be something to do with the new GPU rendering process but either way,
>>> Chrome should not be able to crash X. When X crashes, the system is
>>> completely unusable, does not respond to keypresses and must be power
>>> cycled to become usable once more.
>>
>> Very likely an intel driver problem. However seems already fixed. Read this:
>> http://lists.debian.org/debian-x/2010/10/msg00057.html
>>
>> If you can, try yourself using the intel driver from experimental.
>> Ciao.
>>
>> Cesare.
>>
>
>
>
> --
> Jonathan E. Magen
> 203-936-9665
> http://www.yonkeltron.com
> AIM: SuspectAshkenaz
> GTALK: yonkeltron@gmail.com
> http://twitter.com/yonkeltron
> ב"ה
>
--
Jonathan E. Magen
203-936-9665
http://www.yonkeltron.com
AIM: SuspectAshkenaz
GTALK: yonkeltron@gmail.com
http://twitter.com/yonkeltron
ב"ה
Reply to: