Hi ,
First I want to thank u for this nice program.
Second i will start with bugs ) I use OPEN SUSE 10, KDE 3.4.2, KTorrent 1.1.
2.1. When torrent is nearly downloaded (about 98%-99%) often Ktorrent crash. I start it again and it finish download .
2.2. It use a lot of resources (20%-30% CPU and above 100MB RAM) when downloading torrent , seeding is fine.
2.3. In some cases when i click on torrent link in web browser it download torrent in temp directory, but start a new copy of program instead of using running one.
2.4. Finally I don't like that KTorrent use double disk space - one for temp (tor0,tor1,tor2 and etc). and two for saved copy of download file(s) , Recently i start not to save downloaded torrent , but to use temp copy. Is it possible to change this.
Download , Save files , Clear temp dir, Use saved one for seeding.

P.S. Sorry for my owful english.

Invincible wrote:Hi ,
First I want to thank u for this nice program.
Second i will start with bugs ) I use OPEN SUSE 10, KDE 3.4.2, KTorrent 1.1.
2.1. When torrent is nearly downloaded (about 98%-99%) often Ktorrent crash. I start it again and it finish download .

Got any backtraces for those crashes.

2.2. It use a lot of resources (20%-30% CPU and above 100MB RAM) when downloading torrent , seeding is fine.

What computer do you have, ? On my box (64 bit AMD 3500) it will stay around 2 %, memory usage is about the same. Even on my other computer (an old 1 Ghz P3) it stayed below 5 %.

2.3. In some cases when i click on torrent link in web browser it download torrent in temp directory, but start a new copy of program instead of using running one.

That's a KDE buig, doesn't happen to me.

2.4. Finally I don't like that KTorrent use double disk space - one for temp (tor0,tor1,tor2 and etc). and two for saved copy of download file(s) , Recently i start not to save downloaded torrent , but to use temp copy. Is it possible to change this.
Download , Save files , Clear temp dir, Use saved one for seeding.

We don't,, we use symlinks.

I use OPEN SUSE 10, KDE 3.4.2, KTorrent 1.1.
2.1. When torrent is nearly downloaded (about 98%-99%) often Ktorrent crash. I start it again and it finish download .


Got any backtraces for those crashes.

I will post when happen again.

2.2. It use a lot of resources (20%-30% CPU and above 100MB RAM) when downloading torrent , seeding is fine.


What computer do you have, ? On my box (64 bit AMD 3500) it will stay around 2 %, memory usage is about the same. Even on my other computer (an old 1 Ghz P3) it stayed below 5 %.

Duron - 1.4 , 2 weeks ago I was with 256 MB RAM and I couldn't move even a mouse when start downloading.
Now I'm with 768 MB It's fine .

2.3. In some cases when i click on torrent link in web browser it download torrent in temp directory, but start a new copy of program instead of using running one.


That's a KDE buig, doesn't happen to me.

It happend rarely - by the way - I use Opera maybe is from browser.

2.4. Finally I don't like that KTorrent use double disk space - one for temp (tor0,tor1,tor2 and etc). and two for saved copy of download file(s) , Recently i start not to save downloaded torrent , but to use temp copy. Is it possible to change this.
Download , Save files , Clear temp dir, Use saved one for seeding.


We don't,, we use symlinks.

Very sorry I use Ktorrent a couple of months and up to now i didn't realize this

The symlinks where allready in 1.1.

Just goto the temp directory when a download is finished and go into the torX (X being a number), do ls -l and you will see that there is a symlink named cache.

I use OPEN SUSE 10, KDE 3.4.2, KTorrent 1.1.
2.1. When torrent is nearly downloaded (about 98%-99%) often Ktorrent crash. I start it again and it finish download .


Got any backtraces for those crashes.




I will post when happen again.

I'm not sure when Ktorrent crash before 100% or just when download file.
Using qt3 - 3.3.5
Here it is :

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1101724736 (LWP 19756)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#4 0x080a5b46 in bt::ServerAuthenticate::staticMetaObject ()
#5 0x40ef2a8b in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#6 0x40ef2ef0 in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#7 0x4126876c in QSocket::connectionClosed ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#8 0x410f244e in QSocket::sn_read () from /usr/lib/qt3/lib/libqt-mt.so.3
#9 0x41268554 in QSocket::qt_invoke () from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0x40ef2a49 in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x40ef3021 in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0x41235490 in QSocketNotifier::activated ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0x40f11b30 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x40e92d41 in QApplication::internalNotify ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x40e936b9 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x40b9927e in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#17 0x40e86bcd in QEventLoop::activateSocketNotifiers ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x40e40f03 in QEventLoop::processEvents ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x40ea9c39 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x40ea9b36 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x40e9268f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x080670a6 in ?? ()
#23 0x41493ea0 in __libc_start_main () from /lib/tls/libc.so.6
#24 0x08064a41 in ?? ()

We no longer use QSocket, so this bug can't happen anymore.