Summary: | sigabrt during startup --> will not start | ||
---|---|---|---|
Product: | [Applications] ktorrent | Reporter: | Erik Sohns <erik.sohns> |
Component: | general | Assignee: | Joris Guisson <joris.guisson> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Erik Sohns
2007-01-04 19:04:08 UTC
Version ? Name : ktorrent Relocations: (not relocatable) Version : 2.0.3 Vendor: Fedora Project Release : 4.fc6 Build Date: Sat 14 Oct 2006 01:20:55 PM CEST Install Date: Wed 29 Nov 2006 03:53:18 PM CET Build Host: hammer3.fedora.redhat.com Group : Applications/Internet Source RPM: ktorrent-2.0.3-4.fc6.src.rpm Size : 5359930 License: GPL Signature : DSA/SHA1, Sun 15 Oct 2006 03:59:58 PM CEST, Key ID 82ed95041ac70ce6 Packager : Fedora Project <http://bugzilla.redhat.com/bugzilla> URL : http://ktorrent.pwsp.net/ Summary : A BitTorrent program for KDE Description : KTorrent is a BitTorrent program for KDE. Its main features are native KDE integration, download of torrent files, upload speed capping, internet searching using various search engines, UDP Trackers and UPnP support. Have you tried 2.1rc1 yet ? No, not yet. I'm using yum and hence get the updates as they're pushed... It is strange that it happens in operator new, which indicates that it cannot allocate d some memory during startup. I can understand new failing when KT is leaking memory and all your memory is used up, but during start up is very strange. hi, what i noticed is was that KT seemed to "re-check" the downloaded pieces (for all queued torrents ?) during startup (because it had not closed down properly ?). This process would use large amounts of CPU/RAM, to the point where it would just crash... I haven't looked at the code, but does this make sense to you ? We don't do any rechecks at startup |