cocoaforge

I've noticed this over and over on three different machines (G4 Powerbook, G5 Power Mac, 15" Macbook Pro) -- having Cyberduck open for a few hours results in the process using huge amounts of RAM. I just upgraded to the latest version today, and it's currently using, according to Activity Monitor,

36 MB Shared Memory
492 MB Private Memory
507 MB Real Memory
933 MB Virtual Memory

This is four times more than everyone's favorite memory hog, Firefox 2. These values slowly increase, which makes me think there's a memory leak somewhere. Luckily I have tons of RAM, but I still restart it every now and then since I'd prefer that my SFTP client not take up half a gig of memory.

Is this really normal?

-- Gordy

Well, it is cocoa-java, but you could probably run leaks and other utilities to start out with to help find out the cause.

The_Tick wrote:Well, it is cocoa-java, but you could probably run leaks and other utilities to start out with to help find out the cause.

Leaks doesn't see much of the memory as having been leaked:

Process 581: 2392564 nodes malloced for 546118 KB
Process 581: 10675 leaks for 426864 total leaked bytes.

i had problems with 2.6.something, but after upgrading to 2.7.1 i haven't seen any problems (Cyberduck was taking about 1GB of RAM and making everything swap out after i let my computer sleep while cyberduck had connections open) i was going to submit a bug report but that was right about when 2.7.1 came out