Bug 342257

Summary:	KGet eats all memory and locks the desktop
Product:	[Applications] kget	Reporter:	Christopher Yeleighton <giecrilj>
Component:	Core	Assignee:	KGet authors <kget>
Status:	RESOLVED WORKSFORME
Severity:	critical	CC:	justin.zobel, jwrigley7
Priority:	NOR
Version:	2.11.5
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Christopher Yeleighton 2014-12-27 19:21:09 UTC

The amount of memory KGet users grows linearly with the data being downloaded and falls down to the base value of about 40MB when the download has ended.  My desktop stops responding as soon as the memory allocated to KGet exceeds 1GB.  The only way out is to kill the graphics.

Reproducible: Always

Steps to Reproduce:
  1. Tell KGet to download a large file.
  2. Tell the System Monitor to show all processes ordered by memory usage.

Actual Results:  
  2. KGet gradually eats up over 1GB of RAM and the desktop stops responding.

Expected Results:  
  2. Let the memory footprint should of KGet be constant.

Comment 1 Christopher Yeleighton 2014-12-27 20:49:34 UTC

Wrong library loaded.

Comment 2 Christopher Yeleighton 2014-12-27 23:48:58 UTC

I removed the unwanted libraries; KGet behaved for some time but the bug returned.

Comment 3 Christopher Yeleighton 2014-12-27 23:54:40 UTC

Except that it does not release the memory after download finished either this time.

Comment 4 James W 2014-12-31 05:18:42 UTC

Hi there,
I cannot reproduce this with KGet 2.14.3, can you upgrade your version and see if this still occurs? FWIW, bug 64555 seems similar to your not-releasing-memory problem, but it was fixed years ago.

(note: I'm a Google Code-in student)

Comment 5 Justin Zobel 2020-11-24 02:17:39 UTC

I've just tested this on kget 20.08.3 and I can't replicate the issue, it climbs to around 100MB of RAM and then lowers back down once it writes that information to disk.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.

Comment 6 Bug Janitor Service 2020-12-09 04:34:02 UTC

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
mark the bug 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!

Comment 7 Bug Janitor Service 2020-12-24 04:34:51 UTC

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!