On Sunday 21 March 2010 10:12:50 bbac...@googlemail.com wrote:
Now I get the following in the log, looks like a bug?
Mrz 21, 2010 10:08:54:796 (freenet.client.async.SplitFileFetcher,
RequestSender for UID 8681707776366569955 on 4535(236), ERROR):
Multiple decompressors: 2 - this is almost
Now I get the following in the log, looks like a bug?
Mrz 21, 2010 10:08:54:796 (freenet.client.async.SplitFileFetcher,
RequestSender for UID 8681707776366569955 on 4535(236), ERROR):
Multiple decompressors: 2 - this is almost certainly a bug
java.lang.Exception: debug
at
I see that my error report was just ignored, maybe the problem is not
critical (at least for others ^^).
My new feedback: with the latest official version the node still goes
into a 100% loop on my dual core CPU.
But no more log entries are written. The node seem to work normally,
the web
I would try this:
Enable panic button.
Downloading two files so there is at least two files downloading at once (i
think panic button only shows if this is the case).
Click panic button.
Click yes.
it deletes your downloads and history and cache and basically resets your
nodw, BUT, it keeps
No one can help me?
Had a look into the code, and it fails here:
synchronized (FECQueue.this) {
job =
getFECJobBlockingNoDBAccess();
job.running = true;