• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: quartz-wm memory usage
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: quartz-wm memory usage


  • Subject: Re: quartz-wm memory usage
  • From: Greg Parker <email@hidden>
  • Date: Wed, 14 Nov 2007 18:47:44 -0800

On Nov 14, 2007, at 6:20 PM, David Walthour wrote:
However this is a very old message. I have continued to see this problem in Tiger's X11 and now Leopard's X11. I wish I knew what caused it. I just will suddenly realize that the quartz-wm process is eating up a huge amount of ram and it forces me to shut it down. For a long while I switched from quartz-wm to blackbox as my window manager under Tiger because this problem was interfering too much with my work, but I would prefer to get quartz-wm to be stable because of its ability to interleave X11 windows with Mac windows.

It seems the leak is fairly bad when I am running rdesktop to remote to a windows box. When running this app, quartz-wm (not rdesktop) is growing by at least 800KB. For example, the following is the output of two successive runs of leaks on quartz-wm. Notice in the first run, quartz-wm has already leaked two strings of 32 bytes each. In between the two successive runs, I connected to my windows box with rdesktop. After doing so, quartz-wm has grown by about 800kb and this 800kb is never released.

Macintosh:~ dwalthou$ leaks quartz-wm
Process 759: 131224 nodes malloced for 11402 KB
Process 759: 2 leaks for 64 total leaked bytes.
Leak: 0x320a20  size=32	string '_NET_WM_WINDOW_TYPE_NORMAL'
Leak: 0x12efbfe0  size=32	string '_NET_WM_WINDOW_TYPE_NORMAL'
Macintosh:~ dwalthou$ leaks quartz-wm
Process 759: 139616 nodes malloced for 12236 KB
Process 759: 2 leaks for 64 total leaked bytes.
Leak: 0x320a20  size=32	string '_NET_WM_WINDOW_TYPE_NORMAL'
Leak: 0x12efbfe0  size=32	string '_NET_WM_WINDOW_TYPE_NORMAL'

That string leak looks harmless. It's likely to be simple sloppiness during startup, and never hurts anything further.



Also, the amount that it grows by varies each time I run rdesktop because after I closed rdesktop and ran it again, I saw this output from leaks showing that quartz-wm had grown by another 9MB:

Macintosh:~ dwalthou$ leaks quartz-wm
Process 759: 148896 nodes malloced for 21531 KB
Process 759: 2 leaks for 64 total leaked bytes.
Leak: 0x320a20  size=32	string '_NET_WM_WINDOW_TYPE_NORMAL'
Leak: 0x12efbfe0  size=32	string '_NET_WM_WINDOW_TYPE_NORMAL'

Make sure rdesktop really is closing when you do this. Use `top` to look for old copies of rdesktop that didn't really die.


Some tools besides `leaks` that might help indicate where the memory went:
* `heap quartz-wm`. This shows object types and block sizes for allocations in the process. Useful for before-and-after comparisons, especially if you see something like "the number of NSImages goes up by 20 every cycle".
* `vmmap quartz-wm`. This shows the raw virtual memory map for the process. Useful for identifying memory increases that aren't in malloc memory (like window buffers).
* Quartz Debug (in /Developer/Applications/Graphics Tools). First "Show Window List", then look for quartz-wm windows that are created and never destroyed every cycle.



-- Greg Parker email@hidden Runtime Wrangler


_______________________________________________ Do not post admin requests to the list. They will be ignored. X11-users mailing list (email@hidden) This email sent to email@hidden
  • Follow-Ups:
    • Re: quartz-wm memory usage
      • From: "David Walthour" <email@hidden>
References: 
 >Re: quartz-wm memory usage (From: Michael Höfling <email@hidden>)
 >Re: quartz-wm memory usage (From: David Walthour <email@hidden>)

  • Prev by Date: X11 Font issues
  • Next by Date: Re: xterm and UTF-8
  • Previous by thread: Re: quartz-wm memory usage
  • Next by thread: Re: quartz-wm memory usage
  • Index(es):
    • Date
    • Thread