v1.4.0 on WinXP_3 seems to have a memory leak...

0 views
Skip to first unread message

Poseidon

unread,
Nov 6, 2009, 6:32:16 PM11/6/09
to thelastripper-dev
Hi there,
just curious wether this long-term problem may be fixed some time:
while ripping thelastripper uses more and more system memory... in
just about half an hour i grew from 32.900 KB to 53.400 KB. I'll give
him some time, then it'll crash once again ("... has encountered a
problem and will be shut down")
i can't solve the problem by using direct writing to disk without
buffering - but maybe the size grows slower, i'll have to inspect
that.
so - where are this big varaibles which aren't found by the garbage
collector??
it'd be really cool to fix this issue.

Andrey Mikhaylov

unread,
Nov 7, 2009, 7:07:04 AM11/7/09
to thelastr...@googlegroups.com
I already encounter this problem! 1.4.0 crashes regularly. It is
impossible to set it working for a period of time, you have to restart
it manually every once in a while.

Andrey 'lolmaus' Mikhaylov



2009/11/7 Poseidon <googl...@fabian-schink.de>:

Mov GP 0

unread,
Nov 7, 2009, 7:42:48 AM11/7/09
to thelastr...@googlegroups.com
Hi,

I've fixed the crashing on my machine; instead it reports errors
directly to the event log. I just don't know how to get my code into
the dev-branches.

The memory leak keeps. I guess the event handlers are not correctly
unregistered. I'm to lazy to fix it, because it might cause a major
redisign and i don't have time for that. Instead, I'm currently
restarting TLR every 2 or 3 days.


ys, Mov.


2009/11/7 Andrey Mikhaylov <lol...@gmail.com>:

Mov GP 0

unread,
Nov 10, 2009, 3:21:49 PM11/10/09
to thelastr...@googlegroups.com
Hello,

I've still not figured out how to commit code changes back to the svn server. So, you will get a copy with this mail.

In case of an exception, the manager object and the event handlers will be reset and garbage collection takes place to free the memory. This does not solve any memory leak. It simply makes the leak less effective. I've done some memory profiling too. Nothing appears to be odd to me. Probably its a minor bug and needs longer debug sessions.

The report of exceptions to syslog only works with administrator rights. Without these rights, there will be no logging. This should be ok for the end user, while the advanced user still can do analysis of exceptions.


thx, Mov.


2009/11/7 Mov GP 0 <mov...@gmail.com>:
>> --~--~---------~--~----~------------~-------~--~----~
>> You received this message because you are subscribed to the Google Groups "thelastripper-dev" group.
>> To post to this group, send email to thelastr...@googlegroups.com
>> To unsubscribe from this group, send email to thelastripper-...@googlegroups.com
>> For more options, visit this group at http://groups.google.com/group/thelastripper-dev?hl=en
>> -~----------~----~----~----~------~----~------~--~---
>>
>>
>

signature.asc
MainForm.cs

Mov GP 0

unread,
Nov 11, 2009, 5:05:25 AM11/11/09
to thelastr...@googlegroups.com
Hi,

found an little error tonight. here is the bugfix:

Change line 167 and 168 from

EventLog log = new EventLog("TheLastRipper");

to

EventLog log = new EventLog("Application");
log.Source = "TheLastRipper";

thx


2009/11/10 Mov GP 0 <mov...@gmail.com>:
signature.asc
Reply all
Reply to author
Forward
0 new messages