On Sat, 2004-01-17 at 20:56, Alex Deucher wrote:
> I'm not sure if this is a leak per se... the problem is the 2D and 3D
> driver aren't too good at managing memory.  the 3D driver may snag a
> big chunk for a full screen 3D app and then "keep" it.  It's then no
> longer available for the 2D driver resulting in a bad alloc error.  I
> think Alan H. was working on a new memory management system for
> radeon/r200 for post 4.4.

It seems you were correct that this was not a leak.  After tracing
through the various functions that might allocate and free video memory,
I realized that RADEONTransitionTo2d was not being called after the GL
hacks were closed.  It seems that xscreensaver hangs on to something
that prevents this.  After I killed xscreensaver, RADEONTransitionTo2d
was called and Xv started working.

--Jonathan Thambidurai




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to