Version: (using KDE KDE 3.1.3) Installed from: Debian testing/unstable Packages OS: Linux After downloading large files, kget seems to not release memory. On my system, kget starts with 13 MB resident, and after downloading e.g. two 70 MB files, "top" shows kget as having 65 MB memory resident.
Linux Mandrake 9.1 gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk) kde 3.1.3 + kdenetwork-kroupware-1.0.1.tar.bz2 package. I think this may have to do with having "do not delete entry from kget list after successful download". My system was starting to get slow and notices that I had only 12 Meg free of my 512 Meg swap space. Further investigation showed that kget was the culprit. After doing pkill -9 kget and restarting kget over 400 Meg of swap space was released. Some of the kget processes where fairly old. Setting this entry to off seem to fix the problem. Related to this is that if you delete an entry after it has stalled, it would seem the kdeinit process is not released. Hope this helps.
Subject: Re: kget does not release memory On Saturday 20 September 2003 23:12, you wrote: > I think this may have to do with having "do not delete entry from > kget list after successful download". My system was starting to get > slow and notices that I had only 12 Meg free of my 512 Meg swap > space. Further investigation showed that kget was the culprit. After > doing pkill -9 kget and restarting kget over 400 Meg of swap space > was released. Some of the kget processes where fairly old. Setting > this entry to off seem to fix the problem. I do not see such a meny entry in kget. I have an item "Remove files from a list after success", which is marked as "yes". This should do what you suggest. - -erik
Subject: Re: kget does not release memory On Monday, 22 Sep 2003 10:04, you wrote: > I do not see such a meny entry in kget. I have an item "Remove files > from a list after success", which is marked as "yes". This should do > what you suggest. Hello Yes I should have checked what the wording was for this option under the Advanced tab. By default, the "Remove files from a list after success" is ON. I had it switched OFF as I wanted to be able to see what I had downloaded and use the nice feature that if the entry is in the list, kget asks you if you want to download it again. Having it switched OFF seems to result in two things happening (I haven't looked at the code to confirm this but it might help with this bug report): 1. On successful completion of the download the kget process which actually does the download is not released, hence the memory being taken up. 2. Since I have switch it back ON, kget now loads very rapidly, while before it was taking a fairly long time (a couple of minutes?) to load with 100% CPU usage while it was loading. I very quick look at the code seems to suggest that on loading it always creates a Transfer item before checking for the status of the Transfer. Maybe instead of MD_NONE as part of the status, a flag should be stored in the download list so that kget doesn't have to check each and every item in the list when it starts up. Hope this helps.
Due to the move from the make_kget_cool branch back into kdenetwork, this issue has been resolved. For more details about the new KGet please have a look at this page (1st article): http://commit-digest.org/issues/2007-02-25/