[Bug 23085] Radeon KMS: XGetImage very slow, as is Firefox scrolling

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Aug 2 09:20:41 PDT 2009


--- Comment #4 from Joel Feiner <jafeiner at gmail.com>  2009-08-02 09:20:41 PST ---
(In reply to comment #1)
> If Firefox (or any other app, for that matter) uses XGetImage for scrolling,
> it's broken and needs to be fixed.

I've heard that Firefox uses XGetImage when rendering "native" widgets, i.e.,
that it renders the widgets using the native GTK+ libraries and then uses
XGetImage to grab the rendered widget and then uses that image to actually draw
the widgets.  That's why I thought there might be some relationship between
scrolling (pages have widgets) and XGetImage.

> The problem could indeed be due to software fallbacks though. It could really
> be interesting to see profiles obtained with sysprof or oprofile. Please stick
> to a single operation as much as possible during any profile run.

I attached two oprofile reports and unlike last time I tried to file a bug
report, they actually look valid.

Note that I rebuilt my X stack from Git this morning (latest master) and the
kernel code is also up to date, using this Git URL:
http://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git (if you
need a reference point).  The reports include line numbers so I thought that
information might be useful.

> You could also try enabling the fallback debugging code in xserver/exa or the
> driver and see if antything sticks out. But note that some of those debugging
> messages can be red herrings without backing analysis, don't jump to
> conclusions.

I'll attach my Xorg.0.log with the fallback enabled (have to restart X server
for that...)

Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the xorg-driver-ati mailing list