Memory Leaks with Mac Client

I noticed recently when I ran the console app that there is a memory leak from the SL client. Memory leaks are do to poor programing and I have checked this out on several computers and it occurs on all of them. Memory leaks will cause a slowdown in performance that a reboot or logging out and logging back in will usually clear up.

I'd like to ask the Linden programmers to look into this and remedy this problem because this is causing poor performance on the Mac.

Yeah I've seen this too in my console app;

2006-11-28 12:24:28.147 Second Life[265] *** _NSAutoreleaseNoPool(): Object 0x190c7870 of class NSCFDictionary autoreleased with no pool in place - just leaking
2006-11-28 12:24:28.149 Second Life[265] *** _NSAutoreleaseNoPool(): Object 0x190c84d0 of class NSView autoreleased with no pool in place - just leaking
2006-11-28 12:24:28.149 Second Life[265] *** _NSAutoreleaseNoPool(): Object 0x190c84d0 of class NSView autoreleased with no pool in place - just leaking
2006-11-28 12:24:28.149 Second Life[265] *** _NSAutoreleaseNoPool(): Object 0x190c84d0 of class NSView autoreleased with no pool in place - just leaking

just keeps reapeating, not sure if its anything to worry about but it doesnt sound good.

For me, this happens BEFORE I connect. I suspect its caused by the new 'web based'
feeds that show up on the login screen from 2 versions ago. I don't notice any additional leaks after connecting

Same with myself, I was trying to do some diagnostics with teh client after not being able to connect (again) today.

So I am not in world yet, but getting the following leaks:

2006-11-30 11:14:22.717 Second Life[431] *** _NSAutoreleaseNoPool(): Object 0x110b27d0 of class NSMutableParagraphStyle autoreleased with no pool in place - just leaking
2006-11-30 11:14:22.717 Second Life[431] *** _NSAutoreleaseNoPool(): Object 0x110b2980 of class NSCFDictionary autoreleased with no pool in place - just leaking
2006-11-30 11:14:22.719 Second Life[431] *** _NSAutoreleaseNoPool(): Object 0x110b47b0 of class NSView autoreleased with no pool in place - just leaking
2006-11-30 11:14:22.720 Second Life[431] *** _NSAutoreleaseNoPool(): Object 0x110b47b0 of class NSView autoreleased with no pool in place - just leaking
2006-11-30 11:14:22.720 Second Life[431] *** _NSAutoreleaseNoPool(): Object 0x110b47b0 of class NSView autoreleased with no pool in place - just leaking

Hey Guys,

You should submit those logs in a bug report to LL. They may not see this thread, nor see any of the logs. They can't fix any issues without seeing evidence that the problem exists, nor without a bug report for a couple of users.

Bug reports were submitted. In the grand scheme of things, I'd rather have the grid working.

Well i posted one yesterday for what its worth.

Hell yeah, I'm seeing this too. Within a few hours SL has ballooned to over 2GB in VM size and the system starts swapping badly.

This is definitely a new problem as it hasn't happened before. I've had to restart four times today due to SL getting too big for its britches and grinding my Mac Pro to a halt.

-Z

Not to be non-apropos (well, I guess I am) and to risk being hunted down and killed in a rain of one-button mouse bolos to the head -- this is happening on both the mac and PC build of the client, since 1.13.

So this doesn't seem to be a mac-specific issue. The image seems to grow to stupid-o-clock after extended usage since 1.13. I haven't checked Linux. So this may have something to do with the 1.13 changes rather than OS-specific code.

Well this should make some people happy and to know they did look into it, this is on blog on new version fixes;

* Fixed a memory leak on the Intel Mac

Nice job

Out of curiosity, how often are any of you seeing kernel panics?

I'm actually seeing them every couple of days on a 24" iMac core 2 duo, generally preceeded by weird graphics glitches.

I've never run into any application that has fairly consistently been able to induce a kernel panic, before Second Life.

Well so much for the fixed memory leak, looks like its still there, guess i spoke to soon

2006-12-13 12:28:38.835 Second Life[206] *** _NSAutoreleaseNoPool(): Object 0x19136c60 of class NSMutableParagraphStyle autoreleased with no pool in place - just leaking
2006-12-13 12:28:38.835 Second Life[206] *** _NSAutoreleaseNoPool(): Object 0x19139a20 of class NSCFDictionary autoreleased with no pool in place - just leaking
2006-12-13 12:28:38.837 Second Life[206] *** _NSAutoreleaseNoPool(): Object 0x19148ba0 of class NSView autoreleased with no pool in place - just leaking
2006-12-13 12:28:38.837 Second Life[206] *** _NSAutoreleaseNoPool(): Object 0x19148ba0 of class NSView autoreleased with no pool in place - just leaking
2006-12-13 12:28:38.837 Second Life[206] *** _NSAutoreleaseNoPool(): Object 0x19148ba0 of class NSView autoreleased with no pool in place - just leaking
### MRJPlugin: getPluginBundle() here. ###
### MRJPlugin: CFBundleGetBundleWithIdentifier() succeeded. ###
### MRJPlugin: CFURLGetFSRef() succeeded. ###
2006-12-13 12:31:25.191 Second Life[206] *** _NSAutoreleaseNoPool(): Object 0x1911c620 of class NSCFNumber autoreleased with no pool in place - just leaking
2006-12-13 12:31:25.191 Second Life[206] *** _NSAutoreleaseNoPool(): Object 0x2d1ad1e0 of class NSView autoreleased with no pool in place - just leaking
2006-12-13 12:31:25.192 Second Life[206] *** _NSAutoreleaseNoPool(): Object 0x2d1ad1e0 of class NSView autoreleased with no pool in place - just leaking

looks like same message to me?

How do i get the info like above to post?

I am noticing that SL is eating my memory too. I have a widget that shows me running normally at 4, then start SL and it jumps to 11 but after a few hours it gets up to 30.

From ur console, /applications/utilitys/console , console.log

2006-12-15 16:33:09.635 Second Life[418] *** _NSAutoreleaseNoPool(): Object 0x192cc850 of class NSMutableParagraphStyle autoreleased with no pool in place - just leaking
2006-12-15 16:33:09.635 Second Life[418] *** _NSAutoreleaseNoPool(): Object 0x192cca00 of class NSCFDictionary autoreleased with no pool in place - just leaking
2006-12-15 16:33:09.637 Second Life[418] *** _NSAutoreleaseNoPool(): Object 0x192ce830 of class NSView autoreleased with no pool in place - just leaking
2006-12-15 16:33:09.638 Second Life[418] *** _NSAutoreleaseNoPool(): Object 0x192ce830 of class NSView autoreleased with no pool in place - just leaking
2006-12-15 16:33:09.638 Second Life[418] *** _NSAutoreleaseNoPool(): Object 0x192ce830 of class NSView autoreleased with no pool in place - just leaking
Dec 15 16:34:24 john-f-mcgradys-power-mac-g5 crashdump[421]: Second Life crashed
Dec 15 16:34:24 john-f-mcgradys-power-mac-g5 crashdump[421]: crash report written to: /Users/johnfmcgrady/Library/Logs/CrashReporter/Second Life.crash.log

------ and from SL crash log below--

Date/Time: 2006-12-15 16:34:24.359 -1000
OS Version: 10.4.8 (Build 8L127)
Report Version: 4

Command: Second Life
Path: /Applications/Second Life.app/Contents/MacOS/Second Life
Parent: WindowServer [60]

Version: Second Life version 1.13.1.4 (1.13.1.4)

PID: 418
Thread: Unknown

Link (dyld) error:

no suitable image found. Did find:
/Library/Internet Plug-Ins/iPhotoPhotocast.plugin: not a file

I'm getting very similar stuff. Submitted a bug report. Whatever leak they fixed on the Intel Macs didn't seem to get fixed on my G4 powerbook.