Bug 1801085 Comment 5 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Mayank Bansal from comment #4)
> (In reply to Lee Salzman [:lsalzman] from comment #2)
> > (In reply to Jeff Muizelaar [:jrmuizel] from comment #1)
> > > Lee, it looks like we're still getting stuck waiting for source surfaces.
> > 
> > That's because the user left Direct2D remote canvas enabled along with GPU-accelerated canvas, which is not going to play nicely together. Please make sure you have disabled Direct2D canvas before trying to enabled accelerated canvas on Windows.
> 
> I dont know what i am doing wrong. All i know is to enable gpu-canvas, I set gfx.canvas.accelerated=true.
> I have attached my about:support for reference.

You will need to set "gfx.canvas.direct2d.disabled" to true, and then restart. Otherwise the two methods of remoting will try to fight each other, and the result won't be pretty.
(In reply to Mayank Bansal from comment #4)
> (In reply to Lee Salzman [:lsalzman] from comment #2)
> > (In reply to Jeff Muizelaar [:jrmuizel] from comment #1)
> > > Lee, it looks like we're still getting stuck waiting for source surfaces.
> > 
> > That's because the user left Direct2D remote canvas enabled along with GPU-accelerated canvas, which is not going to play nicely together. Please make sure you have disabled Direct2D canvas before trying to enabled accelerated canvas on Windows.
> 
> I dont know what i am doing wrong. All i know is to enable gpu-canvas, I set gfx.canvas.accelerated=true.
> I have attached my about:support for reference.

You will need to set "gfx.direct2d.disabled" to true, and then restart. Otherwise the two methods of remoting will try to fight each other, and the result won't be pretty.

Edit: meant to say "gfx.direct2d.disabled".

Back to Bug 1801085 Comment 5