Apple

On May 25, 2005, at 4:45 AM, Darkshadow wrote:

On May 24, 2005, at 10:42 PM, Nicko van Someren wrote:

Has anyone else noticed a rise in the memory consumption of their applications with moving to Xcode2 and 10.4? Various of my projects seem to be sucking up quite a bit more real memory, as well as a great deal more virtual memory, when deployed on 10.4. I've also noticed this on the Apple applications on 10.4, to the extent that my machine is really dragging; Safari is typically taking up over 100MB of real memory from a virtual set of 0.5GB, which initially made me think it might just have a leak, but Mail.app is chewing over 65MB of real memory and the working set on my own applications seems to have gown too. Despite having 1GB in my laptop it is spending a great deal more time thrashing the disk since moving to 10.4 and I'm wondering if other people on this list have been experiencing the same with their programs.

Incedentally, the Weather Data Dashboard widget is consuming 44MB of real memory _for each instance_, which is sucking away 176MB of my real memory for the four places I watch. Surly there is something wrong with either the widget or the frameworks behind it to be using this much space.

Cheers,
Nicko

I've noticed that when you launch an app for the first time (since the computer has booted up), it uses more memory than subsequent launches. It's been this way since 10.1 or 10.2 - can't remember at the moment when I noticed it. Thought I'd just mention this in case you hadn't looked to see if the memory usage was lower after a relaunch.

References:
	>Working set bloat in Xcode 2 (From: Nicko van Someren <email@hidden>)
	>Re: Working set bloat in Xcode 2 (From: Darkshadow <email@hidden>)