-
Logged In: YES
user_id=1016507
Ignore the last comment. It seem my ISP just started doing
some kind of traffic filtering. Which explains why my
testing was giving consitently bad results. Sorry.
2006-05-22 21:08:40 UTC by duble0syx
-
Logged In: YES
user_id=1016507
After some extensive testing I'd definitely have to agree
that it is not yet fixed. In 0.11 RC1 single transfers are
considerably slower than when 2 different transfer are
going. It is also quite sporadic. I've test the hell out
of this. I have a 1mb upload line transfer peak at 65kB/s.
I think there is something seriously wrong with the
uploading...
2006-05-20 19:06:52 UTC by duble0syx
-
The two incidents listed below in Lopster.rpt are both
cases where the software instantaneously exited. The
first was after it had been online since Tuesday
morning and I was going to delete some downloads that
were queued. The second, I was just sitting in front
of the monitor after having turned the machine off to
clear memory from some previous program use and had
restarted...
2006-04-06 23:19:21 UTC by nobody
-
This is a bug for winlop 0.11 RC1 and most likely RC3
as well. When someone triggers a direct browse of a
large shared library it causes the GUI to freeze before
it starts uploading. In the upload list is shows
"getting info..." during this time. The bug is that on
older PC's and larger shared lists (35000+ in this
case) this freezing causes the transfer to fail to
start and instead...
2006-03-13 00:12:23 UTC by duble0syx
-
Logged In: YES
user_id=1308241
It also crashes on deleting a FINISHED transfer!
me is back to rc1, seems more stable then RC3.
2006-02-18 14:47:17 UTC by kloek
-
Thought I'd add it also refreshes about 1/3 as fast as it
used to as well. So basically during a refresh lopster will
not send or receive data until it is done, but by this time
everyhing has timed out. Hope it's part of the same bug.
2006-02-16 17:54:40 UTC by nobody
-
Thought I'd add it also refreshes about 1/3 as fast as it
used to as well. So basically during a refresh lopster will
not send or receive data until it is done, but by this time
everyhing has timed out. Hope it's part of the same bug.
2006-02-16 17:07:50 UTC by nobody
-
Logged In: YES
user_id=1016507
Lopster seems to automatically output a debug file actually.
After running it from the command line specifying an output
file I noticed there is already a lopster.rpt file
containing a crash log from before. I have attatched it
below. It contains info from 3 crashes, all from the same thing.
2006-02-16 16:38:22 UTC by duble0syx
-
Logged In: YES
user_id=472304
I think I found the problem, looks like it was an old bug
with the filename handling in the files library.
2006-02-16 11:31:31 UTC by danielosmari
-
Logged In: YES
user_id=472304
Well, the RC3 has debug info, try running it from a command
shell with:
lopster > output.txt
And see if you get anything useful. (or, if you happen to
have MSYS/Cygwin, just run it from the shell)
2006-02-16 10:24:41 UTC by danielosmari
