Sorry for continuing this thread but I think there are some open issues: 1. There is a memory leak (or something similar) in the mach64 driver since consecutive calls to the Xv driver fails . (With a call to a GL application in between)
2. Does the lack of feedback indicate that the issue is closed (i.e. bug free or not interesting or resolved)? (I know the funding is non-existing for mach64 , I really appreciate the efforts from Leif D. 3. There is some texmem stuff going on in the main path, is this affecting the mach65-0.0.5 branch? This mail is specifically addressed to Leif D. who has been _very_ responsive (and interested) so far :-) Maybe I should buy a new graphics card, such as Radeon 9000 (or an Nvidia one, god forgive) instead of bothering with old cards?? (even if they work properly) Svante Svante Signell writes: > Leif Delgass writes: > > On Thu, 28 Nov 2002, Svante Signell wrote: > > > > > Leif Delgass writes: > > > > On Wed, 27 Nov 2002, Svante Signell wrote: > > > I have now tested at 1024x768, and everything works OK, but I think there is > > > memory not returned to the card in the 3D driver, see below. > > > > > > > > Actually, those allocations only apply when a GL context is running. > > That's why the message was changed from "Using" to "Will use" -- no memory > > is allocated when that message is logged. When the X server actually > > allocates that memory for the DRI back and depth buffers (when changing > > from no GL contexts to one or more GL contexts -- not including the X > > server's context), you should see "Largest offscreen area available: ..." > At startup of the X server: > (II) ATI(0): Largest offscreen area available: 1280 x 2252 > (II) ATI(0): Will use 511 kB of offscreen memory for XAA > (II) ATI(0): Will use back buffer at offset 0x2ff800 > (II) ATI(0): Will use depth buffer at offset 0x57f800 > Later in the log file: > (II) ATI(0): Largest offscreen area available: 1280 x 2252 > ... > > > You can check /proc/dri/0/clients > > to see the pids of all the DRI clients (there will always be at least one > > for the X server). Note however that when I run KDE, I get a few clients > > listed for some processes that are linked to libGL even though they > > haven't created a full-fledged context and don't cause the X server to > > allocate any memory for 3D. > Only one client remains after exiting from the xsceensaver demo. > cat /proc/dri/0/clients > a dev pid uid magic ioctls > y 0 1904 0 0 6292494 > > BTW: I'm running gnome and sawfish. > > > > I can now reproduce the error for 1280x1024: > > > 1. Run mplayer using the XV driver: Everything is OK > > > 2. Run a 3D application, such as the atlantis demo in xscreensaver > 2a) Exit the atlantis demo, with xscreensaver running in the background. > > > 3. Run mplayer using the XV driver again: Error state occurs > > > X11 error: BadAlloc (insufficient resources for operation) ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
