On Wed, 27 Nov 2002, Svante Signell wrote: > Leif Delgass writes: > > Have you tried a lower resolution? > Not yet.
Try restarting X with 1024x768@16bpp for a while and see if you still have the same problem. > > If it's some sort of memory leak, I'd > > expect that you'd run into it eventually even at a lower resolution. If > > it doesn't happen at lower resolutions, maybe you really just don't have > > enough offscreen memory at 1280x1024. > What is meant with offscreen memory, main memory + card memory or smth else? > free: > total used free shared buffers cached > Mem: 127660 123760 3900 0 9104 44884 > -/+ buffers/cache: 69772 57888 > Swap: 130748 84172 46576 Offscreen memory refers to the on-card memory left over after the framebuffer allocation(s). When there are no GL contexts, the framebuffer memory is equal to display width x display height x bytes per pixel (2 for 16-bit). With GL contexts running, there is an additional back buffer (same size as the 2D "front" framebuffer) plus a depth buffer which is width x height x 2 (depth buffer is always 16-bit). The remaining offscreen memory is used for XAA and XVideo buffers. You can get a BadAlloc when there is not enough offscreen memory left. > > Also, did you run any GL apps > > before starting mplayer or between attempts (or during attempts)? > xscreensaver is running, so some 3D applications are possibly run when > it activates. The box is usually on all day. > > > The > > current code allocates and frees 3D offscreen mem when transitioning from > > no GL contexts to one or more and on transitioning from one or more GL > > contexts to none. It's possible that there's a leak happening on the > > transitions. Also could you send your complete X log after reproducing > > the problem? > Do you mean the XFree86.0.log or an strace log? > See also below. I meant the XFree86.0.log. Could you send the whole thing as an attachment? > > > > --Leif > > > > Can you please describe how memory (both card and main memory) is > allocated and released for 2D and 3D applications: What puzzles me is > that if I start with a fresh X everything is OK, but after the problem > occurs I have to exit X to be able to run the application again. It is > not sufficient to terminate the application to get back to the same > state as as when starting anew. > > Possible causes of the resource shortage can be: > 1. The applications do not return memory when exiting. > 2. X cannot reclaim the memory when the appications exit. > 3. There is a memory leak somewhere. > 4. Something else?? > > Thanks, > Svante > > Selected parts of XFree86.0.log and strace mplayer -vo sdl file.avi below. > > XFree86.0.log > (II) LoadModule: "vbe" > (II) Reloading /usr/X11R6/lib/modules/libvbe.a > (II) ATI(0): VESA BIOS detected > (II) ATI(0): VESA VBE Version 2.0 > (II) ATI(0): VESA VBE Total Mem: 8192 kB > (II) ATI(0): VESA VBE OEM: ATI MACH64 > (II) ATI(0): VESA VBE OEM Software Rev: 1.0 > (II) ATI(0): VESA VBE OEM Vendor: ATI Technologies Inc. > (II) ATI(0): VESA VBE OEM Product: MACH64LP > (II) ATI(0): VESA VBE OEM Product Rev: 01.00 > (II) ATI(0): VESA VBE DDC supported > (II) ATI(0): VESA VBE DDC Level 2 > (II) ATI(0): VESA VBE DDC transfer in appr. 2 sec. > (II) ATI(0): VESA VBE DDC read successfully > (II) ATI(0): Manufacturer: NOK Model: 1b0 Serial#: 33583 > (II) ATI(0): Year: 1998 Week: 9 > (II) ATI(0): EDID Version: 1.2 > ... > (--) ATI(0): ATI 3D Rage LT Pro graphics controller detected. > (--) ATI(0): Chip type 4C42 "LB", version 4, foundry UMC, class 0, revision 0x03 > -- Leif Delgass http://www.retinalburn.net ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
