Bug 25833 (Drago) - Rendering stops, maybe clipping problem.
Summary: Rendering stops, maybe clipping problem.
Alias: Drago
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2009-12-30 07:53 UTC by Drago
Modified: 2019-11-19 08:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Origin outside visibile area from the top. (151.18 KB, image/png)
2009-12-30 07:53 UTC, Drago
no flags Details

Description Drago 2009-12-30 07:53:16 UTC
Created attachment 32377 [details]
Origin outside visibile area from the top.

Linux 2.6.32
libgl 7.7
xf86-video-ati 6.12.4
libdrm 2.4.17

Using glxgears as benchmark..yes I know it is not really.
In non compositing environment, when glxgears window origin is moved out of current desktop(left and up coordinates), rendering stops (shows last rendered frame, clipped with the window border of-course) frames go high ~4500 as of my hardware RS780(full window visible ~ 1900FPS).
On the other hand, when the glxgears window is under other window, entirely, frames drop down to ~100.
When simultaneously origin outside desktop and covered by window entirely FPS are ~100 too.

In compositing environment, when moving window with GL context, window moves (content black), but GL rendering context stays(and continue to render) on the old place, above any windows. When I finish the move, then it moves in to GL window as usual. When the window origin is moved beyond desktop dimensions, window content stays black.
Comment 1 Drago 2009-12-30 07:56:55 UTC
Now I saw, that on the attachment besides glxgears, on unrefreshed area there is a screen from game Nexuiz, I tested 2 hours ago. Maybe this can help too.
Comment 2 Martin Peres 2019-11-19 08:09:15 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/87.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.