It happens during start or running.
One can fetch backtrace here: http://disk.tom.ru/aggvt1l/1/65736/ktorrent.txt

It seems that allocating some memory failed. How much memory is KT using up ?

George wrote:It seems that allocating some memory failed. How much memory is KT using up ?

Right now according to top it uses virt: 84304 res: 47m
Total amount of virtual memory is pretty big: 1,5GB RAM + 1,5GB SWAP. At least 1GB of virt memory (according to top) is free.

KTorrent's options: memory usage: low.
number of torrents seeded: ~60
number of torrents paused: ~10

So no shortage of memory. Then some bug must be causing KT to try to allocate to much memory. Looking at the code, we must be getting the size of one chunk wrong.

Can you send me all the torrents you are currently running ?

You can find them in ~/.kde/share/apps/ktorrent/

For each torrent there will be a subdirectory named tor0, tor1, tor2 ... These subdirectories contain a file named torrent, which is the torrent. Send all of those to me, then I can load each one of them and check the size of each chunk.

My e-mail address is joris DOT guisson AT gmail DOT com.

The files were sent from email box @rambler.ru

I have got them, I will take at look at them this evening.

George wrote:I have got them, I will take at look at them this evening.

George, is there any results or something?

Other stuff has gotten in the way, but I have nearly checked out all torrents, so far no weird sizes or other anomalies. There are still some left to do, but I'm beginning to think that the moment this happens there is no free memory left.

George wrote:Other stuff has gotten in the way, but I have nearly checked out all torrents, so far no weird sizes or other anomalies. There are still some left to do, but I'm beginning to think that the moment this happens there is no free memory left.

Thanks a lot for information. Is it possible to add check(s) for new[]/new or other allocators?