+++ This bug was initially created as a clone of Bug 1241832 comment 10 +++ With xrender disabled, Firefox performance when connecting using the X server has degraded considerably.
2 years ago
Summary: Investigate disabling xrender on the compositor. → Performance problem(s) when connecting using X server without xrender
(In reply to Milan Sreckovic [:milan] from comment #0) > +++ This bug was initially created as a clone of Bug 1241832 comment 10 +++ > > With xrender disabled, Firefox performance when connecting using the X > server has degraded considerably. X fowarding being slower with xrender compsoiting disabled is not surprising. Do we care about this kind of setup, though? If so we could keep the xrender compositor around and just enable it for this use-case (I am not super found of doing this).
Oh wow. I was wondering what was going on with my ssh -YC... Good to know I just have to toggle a config flag to fix it.
Indeed. Flipped xrender flag back on and browser is working great once more. Thanks. Although, on first restart I did get this crash... https://crash-stats.mozilla.com/report/index/b4bcc4c0-7b4f-4645-a076-736e12160408 But subsequently seems fine now *shrug* Anyway, good to have this working. I use remote ssh -YC for a lot of stuff.
Setting gfx.xrender = true solved the problem of any keyboardinput not being updated grafically. The rendering update took very long and could only be forced by moving the mouse.
Firefox on dev/test servers here was rendering with skewed/unreadable menus (was also kind of slow) when connecting using xrdp. Setting gfx.xrender.enabled;true fixed.
Turning off hardware acceleration worked for me. No more slowness issues. GPUs: NVIDIA GeForce 210, NVIDIA Quadro K4000 (together on same machine for multi-monitor support)
a year ago
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.