Summary: | Seg fault with multiple simultaneous downloads | ||
---|---|---|---|
Product: | [Applications] ktorrent | Reporter: | drvik |
Component: | general | Assignee: | Joris Guisson <joris.guisson> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | drvik |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
drvik
2010-12-08 10:58:33 UTC
*** This bug has been marked as a duplicate of bug 241598 *** I don't understand why this bug has been marked as fixed... I am running 4.0.4 which is long after the http://websvn.kde.org/?view=rev&revision=1137933 commit... if it's fixed then why did this happen?? Created attachment 54330 [details]
New crash information added by DrKonqi
ktorrent (4.0.4) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0
- What I was doing when the application crashed:
Using webbrowser while ktorrent was running in the background....
However this time I noticed that I had a problem with the partition that the torrents are saved to... it is a raid5 with XFS... so I don't know if the partition going offline/down caused ktorrent to crash, or if the torrent crash caused the partition to go offline....
-- Backtrace (Reduced):
#6 memcpy () at ../sysdeps/x86_64/memcpy.S:267
#7 0x00007faf776a5237 in bt::ChunkDownload::piece (this=0x5f8dbd0, p=..., ok=@0x7fff31a4474f) at /usr/include/bits/string3.h:52
#8 0x00007faf776abbde in bt::Downloader::pieceReceived (this=0x25b8690, p=...) at ../../src/download/downloader.cpp:134
#9 0x00007faf7768f315 in bt::Peer::packetReady (this=0x545a5b0, packet=0x7faf3ea55630 "\a", len=<value optimized out>) at ../../src/peer/peer.cpp:283
#10 0x00007faf7769a248 in bt::PacketReader::update (this=0x82e2da0) at ../../src/peer/packetreader.cpp:141
> I don't understand why this bug has been marked as fixed... I am running 4.0.4 > which is long after the http://websvn.kde.org/?view=rev&revision=1137933 > commit... if it's fixed then why did this happen?? Because the fix was not part of 4.0.4, it will be part of the 4.1 branch *** This bug has been marked as a duplicate of bug 241598 *** |