Chrome 15 - canvas killer

We just discovered that latest stable chrome (15.0.874.106) has terrible performances when rendering canvas elements, more details here

the issue seems related to hw acceleration, turning it off should fix the problem.
Thought it was worth to share

BF

Yes, I faced this problem especially while handling canvas image data, wasted 2 days revolving around this issue which didn’t happen until v14.

My problem was, if the parent element of canvas (that has image data) animated with opacity, it didn’t work (probably 0 frame rate). If I set background style (with transparent value) for the parent it just works without disabling hw acceleration. Not sure if this can help every occasion.

how the hell did they released this version as stable is out of my mind.

they basicly broke all canvas apps…. the issue must be solved upstream, have no intention of raping code to find workarounds.

we already have IE for that.

Another tragedy is text smoothness removed if css text-shadow applied. Looks like they are focusing performance at the cost of breaking what actually developed. Web developers can never sleep well if this continues, hope they fix it asap.

With Chrome hardware acceleration is turned off by default right? I remember manually turning it on once but that was for an older version.

CodingJack said
With Chrome hardware acceleration is turned off by default right? I remember manually turning it on once but that was for an older version.

bitfade said

CodingJack said
With Chrome hardware acceleration is turned off by default right? I remember manually turning it on once but that was for an older version.

not anymore, that’s the problem … now you have to turn it off

Ahh I see. Well even when I turned it on manually it never made much of a difference for me as it was still vastly inferior to IE9 and FF.

well problem is chrome 15 with hw accel being utterly slower than 14 without it. still, they enabled by default which is just unbeliavable

We decided to turn off accelerated canvas and revert to the pre-Chrome 15 implementation until we address these performance issues. The switch will happen with the next stable channel update within a week or so. Apologies for the inconvenience this change caused.

^ Awesome!