PDA

View Full Version : Memory leak in 5.0 CVS s/w?



Victor Brilon
2003-11-24, 19:24
Having just installed the nightly build server software, I am watching
it run for about 5-8 minutes and then crashing. Enabling logging shows a
message of "Out of Memory!" being logged.

If I watch the process as it runs, it's growing by about 300K every 5
seconds or so. Obviously this is happening as it's scanning music at
startup. What other debugging can I turn on to help figure this out?

Thanks,
Victor

dean
2003-11-24, 19:54
victor,

how big is your library?
how much memory does your system have?
can you paste the end of the log into a message?

-dena

On Nov 24, 2003, at 6:24 PM, Victor Brilon wrote:

> Having just installed the nightly build server software, I am watching
> it run for about 5-8 minutes and then crashing. Enabling logging shows
> a message of "Out of Memory!" being logged.
>
> If I watch the process as it runs, it's growing by about 300K every 5
> seconds or so. Obviously this is happening as it's scanning music at
> startup. What other debugging can I turn on to help figure this out?
>
> Thanks,
> Victor
>

Victor Brilon
2003-11-24, 20:02
Sorry...meant to include that in the last email but got too happy with
the send button.

System is a Linux box with RH9.
/proc/cpuinfo shows this is:
model name : AMD-K7(tm) Processor
cpu MHz : 548.952

Running 'free' shows:
total used free shared buffers cached
Mem: 255284 214328 40956 0 13488 107136
-/+ buffers/cache: 93704 161580
Swap: 525120 95044 430076


I think the above will wrap, so the 'cached' column should show '107136'

Anyway, looks like plenty of CPU and RAM availability. This system has
been running my old SliMP3 software for the past year or so with no
problem btw.

My library is close to 80 gigs with around 600 albums or so.

/tmp/slimserver.log shows only:
Out of memory!

Which debugging should I enable to show more relevant info? I can turn
it all on and send you a zip of the log file if you'd think it helpful.

Victor
dean blackketter wrote:
> victor,
>
> how big is your library?
> how much memory does your system have?
> can you paste the end of the log into a message?
>
> -dena
>
> On Nov 24, 2003, at 6:24 PM, Victor Brilon wrote:
>
>> Having just installed the nightly build server software, I am watching
>> it run for about 5-8 minutes and then crashing. Enabling logging shows
>> a message of "Out of Memory!" being logged.
>>
>> If I watch the process as it runs, it's growing by about 300K every 5
>> seconds or so. Obviously this is happening as it's scanning music at
>> startup. What other debugging can I turn on to help figure this out?
>>
>> Thanks,
>> Victor
>>

dean
2003-11-24, 20:23
Try starting it from the command line and turn on --d_info

Have your SLIMP3 unplugged and don't use the web interface, just to
keep it simple.

It will spew out a lot of debug information, but if it's really growing
infinitely, we'll see what's going on eventually.

-dean

On Nov 24, 2003, at 7:02 PM, Victor Brilon wrote:

> Sorry...meant to include that in the last email but got too happy with
> the send button.
>
> System is a Linux box with RH9.
> /proc/cpuinfo shows this is:
> model name : AMD-K7(tm) Processor
> cpu MHz : 548.952
>
> Running 'free' shows:
> total used free shared buffers
> cached
> Mem: 255284 214328 40956 0 13488
> 107136
> -/+ buffers/cache: 93704 161580
> Swap: 525120 95044 430076
>
>
> I think the above will wrap, so the 'cached' column should show
> '107136'
>
> Anyway, looks like plenty of CPU and RAM availability. This system has
> been running my old SliMP3 software for the past year or so with no
> problem btw.
>
> My library is close to 80 gigs with around 600 albums or so.
>
> /tmp/slimserver.log shows only:
> Out of memory!
>
> Which debugging should I enable to show more relevant info? I can turn
> it all on and send you a zip of the log file if you'd think it
> helpful.
>
> Victor
> dean blackketter wrote:
>> victor,
>> how big is your library?
>> how much memory does your system have?
>> can you paste the end of the log into a message?
>> -dena
>> On Nov 24, 2003, at 6:24 PM, Victor Brilon wrote:
>>> Having just installed the nightly build server software, I am
>>> watching it run for about 5-8 minutes and then crashing. Enabling
>>> logging shows a message of "Out of Memory!" being logged.
>>>
>>> If I watch the process as it runs, it's growing by about 300K every
>>> 5 seconds or so. Obviously this is happening as it's scanning music
>>> at startup. What other debugging can I turn on to help figure this
>>> out?
>>>
>>> Thanks,
>>> Victor
>>>

Victor Brilon
2003-11-24, 21:42
This got interesting real quick....

If I run the server from the command line, i.e.,
/usr/local/slimserver/slimserver --d_info

then the memory doesn't grow at all. It stays right around 19MB or so
and fluctuates very little while the file scan is going on.

If I start the service via the rc script, then immediately I can see the
memory grow to over 26MB within a minute or two and just progress from
there. While this was going on, I went in the web interface and turned
on d_info on the debug screen.

Looking at the output log, I can't see anything going wrong. I uploaded
the entire thing for you to look at if you'd like. It's about 13MBs
uncompressed, and about 500K compressed. You can find it at
http://victorland.com/slimserver.log.gz

Any suggestions on what else to try and why the daemonized version is
different from the command line version? I haven't changed any of the
options in /etc/sysconfig/slimserver, and that seems to be the only
thing that the rc script version looks at, that the command line doesn't.

Victor

dean blackketter wrote:
> Try starting it from the command line and turn on --d_info
>
> Have your SLIMP3 unplugged and don't use the web interface, just to keep
> it simple.
>
> It will spew out a lot of debug information, but if it's really growing
> infinitely, we'll see what's going on eventually.
>
> -dean
>
> On Nov 24, 2003, at 7:02 PM, Victor Brilon wrote:
>
>> Sorry...meant to include that in the last email but got too happy with
>> the send button.
>>
>> System is a Linux box with RH9.
>> /proc/cpuinfo shows this is:
>> model name : AMD-K7(tm) Processor
>> cpu MHz : 548.952
>>
>> Running 'free' shows:
>> total used free shared buffers cached
>> Mem: 255284 214328 40956 0 13488 107136
>> -/+ buffers/cache: 93704 161580
>> Swap: 525120 95044 430076
>>
>>
>> I think the above will wrap, so the 'cached' column should show '107136'
>>
>> Anyway, looks like plenty of CPU and RAM availability. This system has
>> been running my old SliMP3 software for the past year or so with no
>> problem btw.
>>
>> My library is close to 80 gigs with around 600 albums or so.
>>
>> /tmp/slimserver.log shows only:
>> Out of memory!
>>
>> Which debugging should I enable to show more relevant info? I can turn
>> it all on and send you a zip of the log file if you'd think it helpful.
>>
>> Victor
>> dean blackketter wrote:
>>
>>> victor,
>>> how big is your library?
>>> how much memory does your system have?
>>> can you paste the end of the log into a message?
>>> -dena
>>> On Nov 24, 2003, at 6:24 PM, Victor Brilon wrote:
>>>
>>>> Having just installed the nightly build server software, I am
>>>> watching it run for about 5-8 minutes and then crashing. Enabling
>>>> logging shows a message of "Out of Memory!" being logged.
>>>>
>>>> If I watch the process as it runs, it's growing by about 300K every
>>>> 5 seconds or so. Obviously this is happening as it's scanning music
>>>> at startup. What other debugging can I turn on to help figure this out?
>>>>
>>>> Thanks,
>>>> Victor
>>>>

dean
2003-11-24, 21:52
Are they both using the same prefs file?

Might you have a music folder that's got a recursive link in it or
something?


On Nov 24, 2003, at 8:42 PM, Victor Brilon wrote:

> This got interesting real quick....
>
> If I run the server from the command line, i.e.,
> /usr/local/slimserver/slimserver --d_info
>
> then the memory doesn't grow at all. It stays right around 19MB or so
> and fluctuates very little while the file scan is going on.
>
> If I start the service via the rc script, then immediately I can see
> the memory grow to over 26MB within a minute or two and just progress
> from there. While this was going on, I went in the web interface and
> turned on d_info on the debug screen.
>
> Looking at the output log, I can't see anything going wrong. I
> uploaded the entire thing for you to look at if you'd like. It's about
> 13MBs uncompressed, and about 500K compressed. You can find it at
> http://victorland.com/slimserver.log.gz
>
> Any suggestions on what else to try and why the daemonized version is
> different from the command line version? I haven't changed any of the
> options in /etc/sysconfig/slimserver, and that seems to be the only
> thing that the rc script version looks at, that the command line
> doesn't.
>
> Victor
>
> dean blackketter wrote:
>> Try starting it from the command line and turn on --d_info
>> Have your SLIMP3 unplugged and don't use the web interface, just to
>> keep it simple.
>> It will spew out a lot of debug information, but if it's really
>> growing infinitely, we'll see what's going on eventually.
>> -dean
>> On Nov 24, 2003, at 7:02 PM, Victor Brilon wrote:
>>> Sorry...meant to include that in the last email but got too happy
>>> with the send button.
>>>
>>> System is a Linux box with RH9.
>>> /proc/cpuinfo shows this is:
>>> model name : AMD-K7(tm) Processor
>>> cpu MHz : 548.952
>>>
>>> Running 'free' shows:
>>> total used free shared buffers
>>> cached
>>> Mem: 255284 214328 40956 0 13488
>>> 107136
>>> -/+ buffers/cache: 93704 161580
>>> Swap: 525120 95044 430076
>>>
>>>
>>> I think the above will wrap, so the 'cached' column should show
>>> '107136'
>>>
>>> Anyway, looks like plenty of CPU and RAM availability. This system
>>> has been running my old SliMP3 software for the past year or so with
>>> no problem btw.
>>>
>>> My library is close to 80 gigs with around 600 albums or so.
>>>
>>> /tmp/slimserver.log shows only:
>>> Out of memory!
>>>
>>> Which debugging should I enable to show more relevant info? I can
>>> turn it all on and send you a zip of the log file if you'd think it
>>> helpful.
>>>
>>> Victor
>>> dean blackketter wrote:
>>>
>>>> victor,
>>>> how big is your library?
>>>> how much memory does your system have?
>>>> can you paste the end of the log into a message?
>>>> -dena
>>>> On Nov 24, 2003, at 6:24 PM, Victor Brilon wrote:
>>>>
>>>>> Having just installed the nightly build server software, I am
>>>>> watching it run for about 5-8 minutes and then crashing. Enabling
>>>>> logging shows a message of "Out of Memory!" being logged.
>>>>>
>>>>> If I watch the process as it runs, it's growing by about 300K
>>>>> every 5 seconds or so. Obviously this is happening as it's
>>>>> scanning music at startup. What other debugging can I turn on to
>>>>> help figure this out?
>>>>>
>>>>> Thanks,
>>>>> Victor
>>>>>

Victor Brilon
2003-11-24, 21:54
Sorry...bad form to reply to your own posts.....

Running the server from the command line does grow the memory. It just
slows it down enough, since it has to write all that stuff to the
console, the the growth is not as obvious as quickly. Sorry for the red
herring.

Anyway, what else can I do to diagnose the memory growth?

Victor

Victor Brilon wrote:
> This got interesting real quick....
>
> If I run the server from the command line, i.e.,
> /usr/local/slimserver/slimserver --d_info
>
> then the memory doesn't grow at all. It stays right around 19MB or so
> and fluctuates very little while the file scan is going on.
>
> If I start the service via the rc script, then immediately I can see the
> memory grow to over 26MB within a minute or two and just progress from
> there. While this was going on, I went in the web interface and turned
> on d_info on the debug screen.
>
> Looking at the output log, I can't see anything going wrong. I uploaded
> the entire thing for you to look at if you'd like. It's about 13MBs
> uncompressed, and about 500K compressed. You can find it at
> http://victorland.com/slimserver.log.gz
>
> Any suggestions on what else to try and why the daemonized version is
> different from the command line version? I haven't changed any of the
> options in /etc/sysconfig/slimserver, and that seems to be the only
> thing that the rc script version looks at, that the command line doesn't.
>
> Victor
>
> dean blackketter wrote:
>
>> Try starting it from the command line and turn on --d_info
>>
>> Have your SLIMP3 unplugged and don't use the web interface, just to
>> keep it simple.
>>
>> It will spew out a lot of debug information, but if it's really
>> growing infinitely, we'll see what's going on eventually.
>>
>> -dean
>>
>> On Nov 24, 2003, at 7:02 PM, Victor Brilon wrote:
>>
>>> Sorry...meant to include that in the last email but got too happy
>>> with the send button.
>>>
>>> System is a Linux box with RH9.
>>> /proc/cpuinfo shows this is:
>>> model name : AMD-K7(tm) Processor
>>> cpu MHz : 548.952
>>>
>>> Running 'free' shows:
>>> total used free shared buffers
>>> cached
>>> Mem: 255284 214328 40956 0 13488
>>> 107136
>>> -/+ buffers/cache: 93704 161580
>>> Swap: 525120 95044 430076
>>>
>>>
>>> I think the above will wrap, so the 'cached' column should show '107136'
>>>
>>> Anyway, looks like plenty of CPU and RAM availability. This system
>>> has been running my old SliMP3 software for the past year or so with
>>> no problem btw.
>>>
>>> My library is close to 80 gigs with around 600 albums or so.
>>>
>>> /tmp/slimserver.log shows only:
>>> Out of memory!
>>>
>>> Which debugging should I enable to show more relevant info? I can
>>> turn it all on and send you a zip of the log file if you'd think it
>>> helpful.
>>>
>>> Victor
>>> dean blackketter wrote:
>>>
>>>> victor,
>>>> how big is your library?
>>>> how much memory does your system have?
>>>> can you paste the end of the log into a message?
>>>> -dena
>>>> On Nov 24, 2003, at 6:24 PM, Victor Brilon wrote:
>>>>
>>>>> Having just installed the nightly build server software, I am
>>>>> watching it run for about 5-8 minutes and then crashing. Enabling
>>>>> logging shows a message of "Out of Memory!" being logged.
>>>>>
>>>>> If I watch the process as it runs, it's growing by about 300K every
>>>>> 5 seconds or so. Obviously this is happening as it's scanning music
>>>>> at startup. What other debugging can I turn on to help figure this
>>>>> out?
>>>>>
>>>>> Thanks,
>>>>> Victor
>>>>>