Bug 274138 - ram usage seems a bit high after playing large number of hands of FreeCell
Summary: ram usage seems a bit high after playing large number of hands of FreeCell
Status: RESOLVED WORKSFORME
Alias: None
Product: kpat
Classification: Applications
Component: general (show other bugs)
Version: 3.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-25 20:59 UTC by bill p. (aka google01103)
Modified: 2023-01-18 10:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description bill p. (aka google01103) 2011-05-25 20:59:09 UTC 
Version:           3.5 (using KDE 4.6.3) 
OS:                Linux

When I load Kpat ram used (per system monitor) is 79,114K, but leaving the app open and playing a fair number of hands the ram now shows at 164,000K which seems high.

Game played is FreeCell

Reproducible: Didn't try

Steps to Reproduce:
open play, play a lot 

Actual Results:  
higher ram usage

Expected Results:  
wouldn't expect ram to increase this much
Comment 1 bill p. (aka google01103) 2011-06-01 14:19:54 UTC 
so, as of today I'm not seeing this but did find a post on the forums with similar experience http://forum.kde.org/viewtopic.php?f=21&t=95163&p=196707&hilit=kpat#p196707
Comment 2 polong 2011-12-05 15:29:57 UTC 
+1
Comment 3 Andrew Crouthamel 2018-11-06 15:11:11 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-18 03:31:47 UTC 
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2022-12-21 23:58:26 UTC 
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2023-01-05 05:25:28 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 Stephan Kulow 2023-01-18 10:23:56 UTC 
too old to care - and 164M is possibly not worth a smile nowdays :)