PDA

View Full Version : Anyone else seeing evidence of a memory leak?



JJZolx
2005-11-28, 14:59
This has been an ongoing thing on my system. Currently I'm running SlimServer 6.5b1, but I don't think it's attributable to running that version, as I was having the same issues with 6.2.x.

Here's my setup:

- Windows XP Pro (P4, 1GB RAM)
- SlimServer 6.5b1, Perl version
- plugins running: Date & Time, Random Mix, xPL Interface
- debugging options: -d_info -d_sql
- Running as a Windows service using srvany
- using MySQL 4.1

In Windows task manager the SlimServer process shows up as "perl.exe". Starts off at about 53MB, then grows continuously. Currently it's using 127MB after running for about three days (75 hours). MySQL uses another 30MB, but that's pretty consistent.

I was following another forum thread a couple of days ago and enabled the -d_sql debugging option just for grins. That seems to have accelerated the growth of the memory footprint, so I wonder if the leak is somewhere within the debugging/logging system.

radish
2005-11-28, 17:09
I'm not seeing it, but will provide my data also so you can maybe narrow down the culprit. Process is currently using 74mb and has been running for over a week.

- Windows XP Pro SP2 (Athlon, 512mb RAM)
- SlimServer 6.2.1 exe version
- plugins enabled: bookmarks, date & time, favorites, grab playlist, podcast browser, random mix, rescan library, rss ticker, save playlist, server health, snow ss, vis ss, xml-rpc
- debugging options: none
- Running as a Windows service
- using sqlite

Dan Sully
2005-11-29, 18:03
* JJZolx shaped the electrons to say...

>I was following another forum thread a couple of days ago and enabled
>the -d_sql debugging option just for grins. That seems to have
>accelerated the growth of the memory footprint, so I wonder if the leak
>is somewhere within the debugging/logging system.

Jim - we keep a small amount of the log in memory - so that the when
accessing log.txt - it can be served right away, and we don't need to
open/write/close a file every time a log message happens.

Try adjusting your 'livelog' setting to be 0 ?

-D
--
They're techno trousers, ex-NASA, fantastic for walkies!

JJZolx
2005-11-29, 18:31
* JJZolx shaped the electrons to say...

>I was following another forum thread a couple of days ago and enabled
>the -d_sql debugging option just for grins. That seems to have
>accelerated the growth of the memory footprint, so I wonder if the leak
>is somewhere within the debugging/logging system.

Jim - we keep a small amount of the log in memory - so that the when
accessing log.txt - it can be served right away, and we don't need to
open/write/close a file every time a log message happens.

Try adjusting your 'livelog' setting to be 0 ?
I take it that setting is only available by editing server.pref? In any case I've edited it and restarted the server - I think it was set to something like 10k. We'll see what happens. I should probably also try running with debugging and logging completely disabled to really see if that's where the problem might be.

JJZolx
2005-12-10, 21:50
The livelog setting of 0 had no effect - the service still continually grew and grew in size. Tonight I finally got around to testing with all debugging turned off and the SlimServer service now never grows past about 59MB. So, I can only conclude that it's something in the debugging code.

Wouldn't surprise me if few others ever saw the problem. I doubt that many people run SlimServer on a daily basis with debugging turned on, with the exception of developers. Developers, though, are probably starting and stopping the service so often that it never has a chance to grow much.

tim
2006-01-31, 23:08
I have a memory leak "caught on tape"

http://mywebpages.comcast.net/t.limon/slim/P1310860.MOV

I'm running XPSP2 on a headless dedicated box (512Meg Kingston ram, AMD Duron 800 Mhz, Shuttle Mobo) SlimServer Version: 6.2.1 - 5194 - Windows XP - EN - cp1252

Every 3 or 4 days, I get "Virtual memory low" warnings, and it bombs.

I use it mainly for shoutcast stations. I have 3 SB2's (1 wired and 2 wireless, all synched) Can you help me?

Dan Sully
2006-02-01, 10:13
* tim shaped the electrons to say...

>http://mywebpages.comcast.net/t.limon/slim/P1310860.MOV
>
>I'm running XPSP2 on a headless dedicated box (512Meg Kingston ram, AMD
>Duron 800 Mhz, Shuttle Mobo) SlimServer Version: 6.2.1 - 5194 - Windows
>XP - EN - cp1252
>
>Every 3 or 4 days, I get "Virtual memory low" warnings, and it bombs.

Please try the 6.2.2 nightlies - this should be fixed there.

http://www.slimdevices.com/dev_nightly.html

-D
--
<iNoah> I think someone should create a magazine for computer peripherals, called Card & Driver

tim
2006-02-06, 23:18
Alright, I tried the 6.2.2 maintainance release. It worked for a few days and then bombed again.

Sooo... I thought I'd try the 6.2b5 nightly (SlimServer_v2006-02-06.exe) but the freaking skins are all messed up. Great, so I'll just switch back to the 6.2.2 and live with it for a while, right?

WRONG! Now the server begins to run and then exits abruptly. Reboot, same behavior.

Okay lets try the 01-31-nightly... Nope. WTF? No matter which of the versions I install, I get the same behavior. No I can't get any of them to run... Any more ideas?

Patrick Dixon
2006-02-07, 02:28
IIRC you need to delete slimserversql.db when 'regressing' from 6.5, because the database structure is not backward compatible. SS should then do a rescan when it starts.

tim
2006-02-07, 06:41
I ended up un-installing it and re-installing the prior version. It works now, but I've learned not to just blindly follow others advice without lurking in the beta forums for a while to see what other oddities will crop up. Thanks for the tip.