Re: quartz-wm memory once again

I ran leaks against it, and it only found two strings totaling 64 bytes I had to restart since so I don't have which ones in particular on hand, but that's not anywhere near enough to really matter.  Will get it anyway if I can.

It starts expanding as soon as I start the process, but it's nowhere near linear, it expands faster the longer its been running, or seems to anyway.  Since I restarted X just recently I'll set something up to pull heaps periodically and mark when the system goes to sleep so it'll be easier to watch, and once it gets back up to size I'll pull a core (may be a few days).

Thanks for the quick response.

On Wed, Apr 30, 2008 at 7:45 PM, Ben Byer <email@hidden> wrote:

On Apr 30, 2008, at 12:42 PM, Tom Scogland wrote:

Hi,

I seem to be having a similar problem to the one detailed in http://lists.apple.com/archives/x11-users/2007/nov/msg00728.html except that I've run the 10.5.2 version, 2.2.1, and 2.1.4 and all of them end up eating 300+ MB of memory after a few days.  The confounding part is, the only thing I have run under X11 in those days is xterms, plain old everyday xterms, no rdesktop or anything of the kind and it still blows up.  It seems to expand most across sleeps for some reason.  

I'm running leopard 1.5.2 on a  MBP, and currently running X11.app version 2.1.4.  Attached is the output from `heap quartz-wm` with it currently sitting at 368.85MB of ram.  If there is any assistance I can provide to make this problem go away I would be delighted to oblige.

Hmm..

Zone DefaultMallocZone_0x43000: 1027005 nodes (394483904 bytes) 

                                     CLASS_NAME  TYPE               BINARY     COUNT     BYTES       AVG

                                     ==========  ====               ======     =====     =====       ===

                                     NSCFString  ObjC       CoreFoundation    394160 121666720     308.7

                                       NSCFData  ObjC           Foundation    375724 136259904     362.7

                                   <non-object>                               130922 132499200    1012.0

                          NSConcreteMutableData  ObjC           Foundation    125254   4008128      32.0

                                     __NSCFDate  ObjC       CoreFoundation       182      2912      16.0

Those first three lines are highly suspicious.   For reference, I left quartz-wm running overnight on my iMac, and slept it a couple of times, and I have:

                                   <non-object>                                 3409    258272      75.8

                                     NSCFString  ObjC       CoreFoundation      1055     28832      27.3

                                 NSCFDictionary  ObjC           Foundation        88      5824      66.2

                                      NSCFArray  ObjC           Foundation        54      1760      32.6

                                     NSCFNumber  ObjC           Foundation        39       624      16.0

The next time you see this, can you try running "leaks quartz-wm" and see if it reports any leaks?   If not, my next suggestion would be to try running Amit Singh's gcore program (source at http://www.osxbook.com/book/bonus/chapter8/core/download/gcore-1.3.tar.gz, more info at http://www.osxbook.com/book/bonus/chapter8/core/) to take a coredump of the bloated process -- if you could then get that file to me, I should be able to see what's taking up so much space.

How soon does it start expanding?   Does it start growing linearly as soon as you start running it, or do you need to run it for a few days before it starts growing?

-b

--
-N
AKA:Tom Scogland
I am enough of an artist to draw freely upon my imagination. Imagination is more important than knowledge. Knowledge is limited. Imagination encircles the world.
-Albert Einstein