I have just committed protocol encryption. It is now in SVN.

To compile the code you need the GNU MP library installed. This is probably installed by default on most distributions (but the development packages probably not). In your package manager look for libgmp and libgmp-dev or something like that.

You need to enable the encryption in the preference dialog (under general).

This is GREAT news

There are less reasons to use azureus every week, and this one is a big one in that.

Thanks for the hard work

Is there a list of other changes committed to in the SVN?

George wrote:I have just committed protocol encryption. It is now in SVN.

THANKS !

google01103 wrote:Is there a list of other changes committed to in the SVN?

I always check svntalk, but that's missing some commits short after 1.2 though.

Thanks George.

I will download it now and test it.

Bye

Well i downloaded and try it

Then... the BIG problem
I run ktorrent 1.3dev (last svn version) with my user.
The user allready have ~/.kde/share/apps/ktorrent (from my installed ktorrent (using Gentoo portage ktorrent 1.2)
And suddenly my Hd start to work (REALLY WORK)

ktorrent, starts to fullfill my /home partition with
~/.kde/share/apps/ktorrent/tor0/current_chunk.tmp
When i kill ktorrent this file was about 6.4G

Well, then i move out my previous ~/.kde/share/apps/ktorrent/ letting the svn version generates his own.

Everything looks fine except for 1 little thing

If i load the infowidget plugin, ktorrent crash with this error

Code: Select all

lt-ktorrent: symbol lookup error: /usr/lib64/kde3/ktinfowidgetplugin.so: undefined symbol: _ZN2bt6BitSetC1Em

Besides that it seems that encryption support works good.

BTW it will be good if there is some documentation about plugins so everybody could write his own plugin.
i.e. i want to do a "plugin" that pipes to a file.tmp some info and then use this info in my conky (or gkrellm2).
That could be: current peers, seeders, Down Speed (from the tor1 or total)...etc
I dig around for a while, but dont get it. Maybe other day with more time i can do it all by my self.

Good Bye
And Keep the Good work

KarMax wrote:Everything looks fine except for 1 little thing

If i load the infowidget plugin, ktorrent crash with this error

Code: Select all

lt-ktorrent: symbol lookup error: /usr/lib64/kde3/ktinfowidgetplugin.so: undefined symbol: _ZN2bt6BitSetC1Em

I had this problem. I don't know where Gentoo installs KTorrent, but it's not the same as the ./configure does. unemerge ktorrent then reinstall from SVN and the infowidget shouldn't crash it.

Installed the SVN version and encryption seems to be working for me. Good work!

I found this afternoon my system was totally unresponsive (several seconds to open a terminal window), then I noticed KT was in the state described by KarMax above: memory filled up and hard disk working like hell...
Since KT might not be the sole culprit I rebooted the system that had some two weeks of uptime, and it seems all is running OK by now

jyhelle wrote:I found this afternoon my system was totally unresponsive (several seconds to open a terminal window), then I noticed KT was in the state described by KarMax above: memory filled up and hard disk working like hell...
Since KT might not be the sole culprit I rebooted the system that had some two weeks of uptime, and it seems all is running OK by now

The hard disk running like hell might have something to do with pages being loaded in and out of memory.

Maybe a memory leak somewhere in the encryption code ? Allthough there isn't much dynamic allocation going on there. When you encounter this again, can you make sure it is KT, using top or something like that.

George wrote:The hard disk running like hell might have something to do with pages being loaded in and out of memory.

Maybe a memory leak somewhere in the encryption code ? Allthough there isn't much dynamic allocation going on there. When you encounter this again, can you make sure it is KT, using top or something like that.

Linux kafka 2.6.16-gentoo-r7 #1 Tue May 9 21:27:39 UTC 2006 x86_64 AMD Athlon(tm) 64 Processor 2800+ GNU/Linux

The problem cames when you have a previous version of ktorrent installed using emerge (if you want you can check the ktorrent-1.2.ebuild (v1.2)
My files and config are stored in ~/.kde/share/apps/ktorrent.
Then when you make and run (i dont do make install) the svn version, ktorrent start to create a tmp file (i asume that this file will never stop growing). The file is current_chunk.tmp

I have conky running, so when this problem "startup" i can confirm that the problem was ktorrent.
Maybe its a wrong check (file size, cant erase...) with "current_chunks". dont know.


It will be good if someone can test this problem too.
I dont need to restart my system. (have different partitions and some user limitations) so "beware" when you test this problem.


BTW the idea of the scheduller plugin and the autoload torrents is excellent.
Keep the good work

I think I know what is causing this problem :

It's actually a fix to a bug, which causes the current_chunks file to break on 64 bit platforms. This only happens with old downloads, new downloads have a proper current_chunks file and work.

I made a sticky about it.

So the best way to deal with this is to remove the current_chunks file of all torrents you started before you upgraded. You will loose some data but not much.

I was a few days gone because of a telco hop, sry.

I experience the same problem as KarMax on my 32bit kubuntu using latest svn. A few days ago ktorrent consumed a lot of ram (far more than normally), but at that time i guessed i crewed up kubuntu. Now when i start ktorrent, i see something alike KarMax happening here.

OK, i had removed all current_chunks files and started ktorrent, after that ktorrent crashed:

Code: Select all

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(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)
(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)
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1232803616 (LWP 6391)]
(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)
(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)
(no debugging symbols found)
[KCrash handler]
#6  0x080813b5 in typeinfo for QPtrList<kt::TorrentInterface> ()
#7  0xb5cb456e in kt::BWScheduler::trigger (this=0xb5cd4580)
    at bwscheduler.cpp:175
#8  0xb5cb2813 in kt::SchedulerPlugin::load (this=0x84f8c20)
    at schedulerplugin.cpp:93
#9  0xb7ebac08 in kt::PluginManager::load () from /usr/lib/libktorrent.so.0
#10 0xb7ebb0d7 in kt::PluginManager::loadPluginList ()
   from /usr/lib/libktorrent.so.0
#11 0x08069bb3 in kt::CompareVal<unsigned long> ()
#12 0x0805d957 in QGList::count ()
#13 0x0806e7e1 in QValueList<QString>::detachInternal ()
#14 0xb779b610 in KUniqueApplication::processDelayed ()
   from /usr/lib/libkdecore.so.4
#15 0xb779cd87 in KUniqueApplication::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#16 0x0806e447 in QValueList<QString>::detachInternal ()
#17 0xb706ee29 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#18 0xb7401e1a in QSignal::signal () from /usr/lib/libqt-mt.so.3
#19 0xb708c5a0 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#20 0xb7094090 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#21 0xb7004dc6 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#22 0xb7004fc2 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#23 0xb7789d7d in KApplication::notify () from /usr/lib/libkdecore.so.4
#24 0xb6f960ef in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#25 0xb6ff67b3 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#26 0xb6fa9eff in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#27 0xb701d8b7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#28 0xb701d7da in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#29 0xb70038d5 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#30 0x0805b79f in ?? ()
#31 0xb688bea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#32 0x0805b451 in ?? ()


So i uninstalled ktorrent and rm the svn folder, and after that i co & make again.
All is fine again.
Now i'll keep my eyes on the ram usage i experienced before.