Version: 7.4 - 25015 @ Sat Feb 14 01:01:02 PST 2009
Hostname: hal.home.lan
Server IP Address: 192.168.1.5
Server HTTP Port Number: 9000
Operating system: Red Hat - EN - utf8
Platform Architecture: i686-linux
Perl Version: 5.8.8 - i686-linux-thread-multi
MySQL Version: 4.1.20
Total Players Recogniz
Atached part of the messages file from my server a ClarkConent comunity
edition 4.2 linux .
Btw normally my server rarely uses more than a third of its physical
memory.
+---+
|Filename: messages.zip
By using the free -m comand i can see one thing.
if i'm running squeezecenter on the server the memory usage is
increasing very slowly over time.
if i'm not running squeezecenter memory usage is constant over time.
the effect is very slow it will probably take 5 -8 hours to crash the
machine ?
My Windows Home Server started crashing every two days beginning with
7.3.x and same problem with betas - received a system error and
reboots automatically. Haven't seen others with the same problem, so I
uninstalled SC. The server has been stable for weeks now, so it
definately was SC. I'm run
> My Windows Home Server started crashing every two days beginning with
> 7.3.x and same problem with betas - received a system error and
What system error? Whatever SC does, it shouldn't make your system reboot. The
only reason I could imagine was a while back, when excessive logging might have
I haven't had time to track memory usage yet, but I've also seen
problems with 25015 where after hours of usage, SC will slow down and
eventually hang.
--
Fletch
Fletch's Profile: http://forums.slimdevices.com/member.php?u
Fletch;397057 Wrote:
> I haven't had time to track memory usage yet, but I've also seen
> problems with 25015 where after hours of usage, SC will slow down and
> eventually hang.
This is on Linux, of course.
--
Fletch
Fl
mherger;397049 Wrote:
> > My Windows Home Server started crashing every two days beginning with
> > 7.3.x and same problem with betas - received a system error and
>
> What system error? Whatever SC does, it shouldn't make your system
> reboot. The only reason I could imagine was a while back,
Hi there, some On Toppic here from me. Have any one managed to track
this memory leak in 7.4 25015 LINUX version Yet ?
I'm away from home now (lot of work what economic crise ? ) so I can
not test this further ?
I'm not a programmer so i'm not so good at running, the kind of
software you need to
