Massive Finder Memory Leaks

[Lindono]

Process: Finder [484]
Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Load Address: 0x10d190000
Identifier: com.apple.finder
Version: 10.7.3 (10.7.3)
Build Info: Finder_FE-751003013000000~4
Code Type: X86-64 (Native)
Parent Process: launchd [426]

Date/Time: 2012-07-15 15:57:41.045 -0400
OS Version: Mac OS X Server 10.7.4 (11E53)
Report Version: 7

leaks Report Version: 2.0
Process 484: 14986745 nodes malloced for 1329243 KB
Process 484: 433906 leaks for 55244016 total leaked bytes.

Now, I don't think this is normal... Finder should not have that many leaks. This is from the "leaks" command incase anyone is interested. Finder keeps getting extremely sluggish over time, and I'm thinking this may have a lot to do with it. I'm curious about other people's Finders though, or if it's just me.
I'd like to see the results of this command from people:

leaks -nostacks -nocontext Finder

Thanks.

EDIT: Just give the the top part though, I just want to know the number of leaks. Thanks.
EDIT2: Come on guys, this isn't a hard thing to do. I really would like to have this data...

 

[meme1255]

Process: Finder [495]
Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Load Address: 0x10e02e000
Identifier: com.apple.finder
Version: 10.7.3 (10.7.3)
Build Info: Finder_FE-751003013000000~4
Code Type: X86-64 (Native)
Parent Process: launchd [477]

Date/Time: 2012-07-15 23:52:19.055 +0200
OS Version: Mac OS X Server 10.7.4 (11E53)
Report Version: 7

leaks Report Version: 2.0
Process 495: 270230 nodes malloced for 67264 KB
Process 495: 724 leaks for 478304 total leaked bytes.

 

[appletechpro]

Unless you've had Finder running for a very, very, very long time then that DEFINITELY does not seem normal.

Process: Finder [265]
Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Load Address: 0x10d1e0000
Identifier: com.apple.finder
Version: 10.7.3 (10.7.3)
Build Info: Finder_FE-751003013000000~4
Code Type: X86-64 (Native)
Parent Process: launchd [251]

Date/Time: 2012-07-15 17:59:50.496 -0700
OS Version: Mac OS X 10.7.4 (11E53)
Report Version: 7

leaks Report Version: 2.0

Process 265: 66242 nodes malloced for 13352 KB
Process 265: 53 leaks for 59152 total leaked bytes.

 

[iwan073]

nvm

 

[Lindono]

Unless you've had Finder running for a very, very, very long time then that DEFINITELY does not seem normal.

Process: Finder [265]
Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Load Address: 0x10d1e0000
Identifier: com.apple.finder
Version: 10.7.3 (10.7.3)
Build Info: Finder_FE-751003013000000~4
Code Type: X86-64 (Native)
Parent Process: launchd [251]

Date/Time: 2012-07-15 17:59:50.496 -0700
OS Version: Mac OS X 10.7.4 (11E53)
Report Version: 7

leaks Report Version: 2.0

Process 265: 66242 nodes malloced for 13352 KB
Process 265: 53 leaks for 59152 total leaked bytes.

You're right, it isn't normal, although it is interesting that everyone's Finder seems to have a few leaks. My case is particularly bad though, I think I may do a reinstall.

EDIT: I don't understand why Finder should ever be leaking memory though. You'd think that would be something easy to test for. Perhaps Dropbox's code injection into the finder is causing issues? Hard to say. Objective-C is just finicky enough for that to be a possibility, with no garbage collection of course.

 

[Bear]

For all of you running this, are you showing a 10.7.3 finder if you're on OS X 10.7.4?

Process:         Finder [134]
Path:            /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Load Address:    0x107d95000
Identifier:      com.apple.finder
Version:         10.7.3 (10.7.3)
Build Info:      Finder_FE-751003013000000~4
Code Type:       X86-64 (Native)
Parent Process:  launchd [119]

Date/Time:       2012-07-16 09:16:56.665 -0400
OS Version:      Mac OS X 10.7.4 (11E53)
Report Version:  7

leaks Report Version:  2.0
Process 134: 93586 nodes malloced for 12160 KB
Process 134: 560 leaks for 57152 total leaked bytes.
...

Fortunately a Relaunch of the finder clears it:

...
leaks Report Version:  2.0
Process 3815: 49369 nodes malloced for 5295 KB
Process 3815: 0 leaks for 0 total leaked bytes.

 

[Lindono]

For all of you running this, are you showing a 10.7.3 finder if you're on OS X 10.7.4?

Process:         Finder [134]
Path:            /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Load Address:    0x107d95000
Identifier:      com.apple.finder
Version:         10.7.3 (10.7.3)
Build Info:      Finder_FE-751003013000000~4
Code Type:       X86-64 (Native)
Parent Process:  launchd [119]

Date/Time:       2012-07-16 09:16:56.665 -0400
OS Version:      Mac OS X 10.7.4 (11E53)
Report Version:  7

leaks Report Version:  2.0
Process 134: 93586 nodes malloced for 12160 KB
Process 134: 560 leaks for 57152 total leaked bytes.
...

Fortunately a Relaunch of the finder clears it:

...
leaks Report Version:  2.0
Process 3815: 49369 nodes malloced for 5295 KB
Process 3815: 0 leaks for 0 total leaked bytes.

You're right, it is a 10.7.3 Finder. That is a little unusual.

 

[Mal]

For all of you running this, are you showing a 10.7.3 finder if you're on OS X 10.7.4?

That's normal. The Finder isn't updated with every point release, so sometimes it'll be a version number or two behind. They used to use numbers that were even further off at times, which could be confusing.

jW