Bug 1687106 - kpat uses a lot of memory
Summary: kpat uses a lot of memory
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kpat
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-09 20:44 UTC by Pierre Juhen
Modified: 2019-05-12 22:26 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-12 22:26:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pierre Juhen 2019-03-09 20:44:52 UTC
Description of problem:

kpat uses a lot of memory, until it starts to use swap. You have  to kill it to get control of KDE again.


Version-Release number of selected component (if applicable):

kpat-18.12.2-1.fc29.x86_64

How reproducible:

Not systematic, but very often.

Actual results:

kpat and KDE becomes very, very slow, unusable

Expected results:


Additional info:

Comment 1 clifford snow 2019-03-10 19:40:39 UTC
I'm seeing similar slow downs with kpat. It will often die or stop responding needing a force kill to exit.

I have kpat version 3.6 on f29. 

Not sure if this will help, but top reports the following when kpat is first started
VIRT=863295
RES=97984 
SHR=64964

Whiching to another game can cause the memory requirements to jump
VIRT=1098908
RES=349600 
SHR=66588

Memory needs increase as you continue to play although they may decrease at times.

VIRT=1104736 
RES=355192  
SHR66588

Comment 2 Remi Collet 2019-03-22 08:02:02 UTC
It is unusable,

Tried kpat-18.12.2-1.fc29.x86_64 and 18.12.3 from rawhide

Comment 3 Kekke 2019-04-25 13:35:30 UTC
kpat-18.12.2-1.fc29.x86_64 on Fedora 29 is very slow/hangs and starts to consume 100% cpu.
According to other forums the problem disappears if "Solver" is disabled.

After downgrading to kpat-18.04.3-1.fc29.x86_64 everything works as expected and cpu usage is negligible.

Comment 4 Rex Dieter 2019-04-25 14:07:37 UTC
Ideally, please report this upstream to bugs.kde.org

We (downstream) have limited resources to debug/fix this ourselves, at least not with upstream collaboration.

Comment 5 Pierre Juhen 2019-05-12 22:26:10 UTC
Supposed to be closed on kpat 19.04. Not tested


Note You need to log in before you can comment on or make changes to this bug.