Registered Member
|
I was using 2.2.5, and downloaded 8 fairly large torrent. That succeeded, eventually, taking about 4 days. However, shortly thereafter, ktorrent would just disappear, and pgrep would show that it was entirely gone.
So I upgraded to 2.2.6, just in case. No go - that would crash shortly after being started, most likely due to the torrents, I assume. Well, seeing that ktorrent.org claimed no more bug fixes in the 2.x stream, and that kde4 apps could run in kde3, I went and installed the minimal kde4 libraries to get ktorrent 3 running. Lo and behold ... that crashes, too. First with 3.0.1, and since I already have kde4 libraries installed, I tried 3.0.2. So that's the versioning. The problem is that ktorrent *does* pick up the 8 torrents I'm still seeding (to get back to a reasonable ratio), and enables 5 of them at seeming random (not that I care which ones). And then after a half hour or an hour, it just locks up and then dies. I'm not really sure what diagnostic information I can gather, though I can tell you that ktorrent is trying to seed ~25GB of data, and the other torrents it still knows about would bring the total to over 50GB. |
Moderator
|
|
Registered Member
|
|
Registered Member
|
Even now, drkonqi doesn't come up when ktorrent goes away. Even the return code is 0, which surprised me.
I even brought up kdevelop, had it create a new kde 3 project (my kdevelop doesn't have templates for kde 4) where I inserted code that said:
and this brought up drkonqi when I ran it from the commandline (didn't when I ran from inside kdevelop), so apparently that part is working ok. I even retried using optimized mode, and that still would bring up drkonqi. |
Moderator
|
|
Registered Member
|
I'm getting this when adding the scheduler plugin ...
and this continues on for a looooong time. It's the easiest-to-reproduce crash, as I don't need to wait long. Unfortunately, it does happen in a back-end process. Apparently, ktorrent forks or something, and gdb thinks the program has exited prior to its completion. Luckily, I remembered about the -p flag: gdb -p $(pgrep ktorrent). That got me attached, and bt then told me about this apparent infinite loop. |
Registered Member
|
Is there any other debug information I can gather that may help with this apparent infinite loop?
I've even gone to a new machine, amd64, all kde4 to start with (i.e., even my desktop is kde4), and I'm getting the same problem, even when I go try to delete a torrent. Thanks, |
Moderator
|
|
Moderator
|
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]