The version v0.24.0 is buggy

[ShadowAbroad]

Sometimes when loosing a connection in the reconnect phase the program take 100% CPU. The only way to stop the program in this case is to kill it. The reconnection phase never succed.
I cant leave the program to download at night because this behaviour.
 :?

If there is any daily build available i can try it.
I've tried in forum but i've been kick off because asking about "daily builds".

Any comments / sugestions.

Tks

[ShadowAbroad]

[4/2/2007 10:49:14 AM] [T3] Article started 20/53 #alt.binaries.dvdr: Smokin.Aces.2007.DVDR-ThP "thp-smokin.aces.r27"
[4/2/2007 10:49:14 AM] [Main] Download queue autosaved in 187ms
[4/2/2007 10:49:16 AM] [T3] Retry 20/53 #alt.binaries.dvdr: Smokin.Aces.2007.DVDR-ThP "aaaa.r27"
[4/2/2007 10:49:16 AM] [T3] Connection lost
[4/2/2007 10:49:16 AM] [T3] Connecting (Free)
[4/2/2007 10:49:16 AM] [T2] Retry 18/53 #alt.binaries.dvdr: Smokin.Aces.2007.DVDR-ThP "aaaa.r27"
[4/2/2007 10:49:16 AM] [T2] Connection lost
[4/2/2007 10:49:16 AM] [T2] Connecting (Free)
[4/2/2007 10:49:16 AM] [T1] Retry 19/53 #alt.binaries.dvdr: Smokin.Aces.2007.DVDR-ThP "aaaa.r27"
[4/2/2007 10:49:16 AM] [T1] Connection lost
[4/2/2007 10:49:16 AM] [T1] Connecting (Free)
[4/2/2007 10:54:14 AM] [Main] Download queue autosaved in 140ms
[4/2/2007 10:59:14 AM] [Main] Download queue autosaved in 109ms
[4/2/2007 11:04:14 AM] [Main] Download queue autosaved in 125ms
[4/2/2007 11:08:00 AM] [Main] Download queue list ageing done in 0ms
[4/2/2007 11:09:14 AM] [Main] Download queue autosaved in 125ms

The T1 T2 and T3 are threads? If it so the 3 threads are suspended or blocked. The program do not take yet the 100% CPU but the last reconnection phase not finished. The buttons Connect or Pause do nothing(no log). Only scheduler buton log something.

[4/2/2007 11:09:17 AM] [Main] Scheduler enabled
[4/2/2007 11:09:20 AM] [Main] Scheduler disabled

If I try to stop the program it get 100% CPU and the process thread number decrement by 3(T1, T2, T3). The program not hung but is not stoping neither. Only a kill can stop it.

[Rdl]

I guess you'll have to wait for next version or go back to whatever you were using before.