Jump to content

client 5.0.540 memory leak?


Recommended Posts

I'm running client 5.0.540 on an iBook with 640MB RAM and Mac OS 10.2.2

 

 

 

My uptime is at 9 days, and the pitond process seems to be sucking up more and more memory. It is currently using:

 

 

 

142 pitond 0.0% 26:32.17 4 51 9095 35.8M 39.5M 50.0M 78.2M

 

 

 

This seems excessive, especialy in comparison to the iBook I back up (384MB RAM Mac OS 10.1.5, client 5.5.528, uptime at 52 days) which uses just a few MBs.

 

 

 

Is there a known memory leak in the current client?

 

 

 

Thanks,

 

 

 

Rand

Link to comment
Share on other sites

And growing...

 

 

 

142 pitond 0.0% 47:25.34 4 63 22210 24.9M 63.3M 72.3M 104M

 

 

 

Running leaks on pitond, shows a definate memory leak:

 

Leak: 0x0541b240 size=894 string '<?xml version="1.0" encoding="UTF-8"?>

 

 

 

 

 

Which seems to me like the above mentioned file is being opened and never closed? Over and over and over?

 

 

 

BTW, this repeats thousands of times, over running by terminal buffer.

 

 

 

I showed this to my brother (an Apple engineer) and he was shocked to see such a memory leak...

 

 

 

Rand

Link to comment
Share on other sites

In reply to:

 

 

Hey Rand, what's leak(s)?

 

 

 

My default 10.2.2 install has no such command; is it part of the Developer's package?

 


 

 

 

I'm sure it is, I don't have any macs that don't have the developer tools installed, so it is already there.

 

 

 

From the man page (just part of the intro)...

 

 

 

In reply to:

 

 

leaks examines a specified process for malloc-allocated buffers which are

 

not referenced by the program. Such buffers waste memory; removing them

 

can reduce swapping and memory usage.

 

 

 

leaks requires one parameter -- either the process id or executable name

 

of the process to examine. It also takes several arguments for modifying

 

its behavior.

 

 

 

Normally, leaks considers a block referenced if a pointer to the block

 

exists somewhere in memory. With the -cycles option, leaks uses the

 

stricter case that the block be referenced by a pointer from blocks known

 

to be reachable by the program. Any block referenced by a pointer in a

 

global variable, or by a pointer from a reachable block, is also reach-

 

able.

 

 

 

For each leaked buffer allocated by malloc, leaks displays the address of

 

the leaked memory and its size. If leaks can determine that the object

 

is an instance of an Objective C or CoreFoundation class, it also speci-

 

fies the name of the class. If the -nocontext option is not specified,

 

it then displays a hexadecimal dump of the contents of the memory. If

 

the MallocHeapLogging environment variable is set, it finally displays a

 

stack trace describing where the buffer was allocated.

 


 

 

 

I had to reboot, so...

 

 

 

165 pitond 0.0% 0:37.45 6 43 55 388K 1.33M 1.41M 19.0M

 

 

 

Rand

Link to comment
Share on other sites

  • 1 month later...

Do you know if anything has been done by Dantz to fix the problems with retrospect client process Pitond?

 

i.e. 1- Pitond sometime starts using all the CPU time

 

2- Pitond uses everyday more and more RAM. At day seventeen after reboot, Pitond is using 200MB in my Mac OS 10.2 server. I had to increase my RAM to 1.5GB to have some stability while using the retrospect client to backup my server.

 

Francis

 

 

 

 

Link to comment
Share on other sites

I have not received any feedback from Dantz regarding this issue. However when I upgraded to 10.2.3 I stopped having the issue with pitond, but I have simular issues with other processes. mDNSResponder was the latest culprit, I killed it last week, and most of my VM swap space was recovered as a result.

 

 

 

However when I restart it is only a matter of a few days before the propelem appears again.

 

 

 

I do not have the Retrospect client running on my 10.2.3 server and it never has a runaway memory issue, so perhaps it really is a Retrospect client issue.

 

 

 

Rand

Link to comment
Share on other sites

Opps spoke too soon...

 

 

 

162 pitond 0.0% 15:02.35 5 43 6120 40.5M 21.7M 60.4M 101M

 

 

 

8:30PM up 6 days, 8:27, 3 users, load averages: 1.36, 0.57, 0.35

 

 

 

not sucking up processor time, but still sucking up a far bit of RAM.

 

 

 

Another iBook here that is running Retrospect client, has never shown these symptoms...

 

 

 

Rand

Link to comment
Share on other sites

  • 1 month later...
  • 3 weeks later...
  • 1 month later...

Dantz has released an update to the Retrospect Client software for Mac OS X. This update is compatible with Retrospect 5.0 for Macintosh as well as Retrospect 6.5 for Windows.

 

Changes made the new Macintosh client software include improved memory management on the client computer as well as a fix for the error -40 File positioning for retropds.22.

 

The new client installer can be downloaded from:

 

ftp://ftp.dantz.com/pub/cs/mac_client_5_1.sit

 

Thanks,

 

Dantz Technical Support

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...