Summary: | Kget crashes on large file (MultiSegmentCopyJob::slotSplitSegment, TransferMultiSegKio::slotSearchUrls) | ||
---|---|---|---|
Product: | [Applications] kget | Reporter: | m.wege |
Component: | general | Assignee: | KGet authors <kget> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andresbajotierra, christian_weilbach, nekkar |
Priority: | NOR | Keywords: | investigated, triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
m.wege
2009-09-19 21:04:38 UTC
Thanks for your report. It is possible that this bug has been already fixed in trunk. Anyway, we are trying to reproduce it. In the meanwhile, if you have the possibility to test again with current development subversion release, would be great. In KDE 4.3.2 the problem still seems to exist. I downloaded a smaller large file (700MB) and Kget started to eat up a lot of memory. The download stopped very early, but still Kget used a lot of memory until I deleted the download. From bug 212562: What I was doing when the application crashed: i have tried to download the file two times before with both times getting stalled at round about the half. the download was to a nfs4 share which is almost full, but this should be no problem as it is still writable. now kget even crashes on startup, which needs serious manual config file fixes/deletion. *** Bug 212562 has been marked as a duplicate of this bug. *** Please retest, the code totally changed in trunk... Lukas Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |