submitdiaginfo, possible memory leak??? (SOLVED)

[brbubba]

Alright what in the hell is going on here??? I have been having Snow Leopard issues from day one where the system becomes unresponsive. I suspected a memory leak of sorts and I finally tracked down the evil culprit. I can quit this process and my issue goes away, but what in the hell is it and why does it keep doing this? (See attached screenshot)

 

[brbubba]

There's very little info on this out there, but I found the MAN page for submitdiaginfo and there is a way to turn it off.

http://developer.apple.com/mac/libr...in/Reference/ManPages/man8/ReportCrash.8.html

I turned it off using the following command:
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist

Hopefully that will kill it permanently.

 

[brbubba]

Well that was a nice try, but it didn't work at all. grrr. Anyone out there?

I thought the command was successful earlier, but apparently not. Now I get this if I try it again.
launchctl: Error unloading: com.apple.ReportCrash.Root

 

[brbubba]

Seriously, anyone out there? I have to force quit this damn process 5 times a day, I'm pulling my hair out over here.

 

[brbubba]

La di friggin da! The 10.6.2 update miraculously fixed things. Now submitdiaginfo just sits there taking up 30MB and 0% CPU cycles. UGH....

EDIT: Nevermind, I had two days of bliss and it starts up again. Screw you apple.

FINALLY SOLVED: So it turns out an old test install of Moxy backup had never been properly uninstalled and was making calls every 10 seconds to perform backups and obviously nothing was happening. I suspect this was creating a massive log file for submitdiaginfo, apple's automated diagnostic tool. Obviously everytime the thing launched it just sucked up massive amounts of RAM because it couldn't handle such a log file. The first fix was to reset the submitdiagtool so it would not longer function unless there was an active crash. Second solution was to deactivate the Moxy backup as a launch daemon. It works great now, but I still blame apple for actually allowing a log file to be created that would cripple submitdiaginfo.