On Sat, Dec 29, 2007 at 04:04:59AM +0100, sebastian.rother@jpberlin.de wrote:

[snip a lot of irrelevant stuff]

quoted text
> I hope you spend some attention to viq after he noticed the bug as well.

Some more people need to send good bug reports, with trace data and
such, for anyone to be able to find what's going on. I sent a request to
close this bug for two reasons: 
1) This box currently crashes even when
doing nothing. First conclusion: faulty hardware, and as it's an old
toy-box I don't feel at the moment like trying to figure out which
component causes this, or whether it's something else.
2) I tried running same torrent on a box with better CPU and same amount
of RAM. It survived the experience, even with more torrents. I tried
running it on a considerably better box, both CPU- and RAM-wise, both
with that torrent and another ones, it survived the experience. Someone
else tested the same torrent on an even slower box, one that is often
running rtorrent. It survived the experience. Someone else tested the
same torrent on yet another machine, which... Yes, you guessed it,
survived the experience. So, untill proven otherwise, with solid proof
and traces, there is no information to work on regarding deciding
whether it's a bug of some sort, or my local problem.
 
quoted text
> 
> Kind regards,
> Sebastian

-- 
viq