Bug 83391 - Kst uses almost 100% cpu after applying fit plugin to large dataset
Summary: Kst uses almost 100% cpu after applying fit plugin to large dataset
Status: RESOLVED FIXED
Alias: None
Product: kst
Classification: Applications
Component: general (show other bugs)
Version: 1.x
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kst
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-14 23:42 UTC by Rick Chern
Modified: 2004-07-13 19:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rick Chern 2004-06-14 23:42:26 UTC
Version:           0.98-devel (using KDE KDE 3.2.1)
Installed from:    RedHat RPMs
Compiler:          gcc (GCC) 3.3.2 20031022  
OS:                Linux

After applying plugin to (200000 or so elements) large vectors, kst uses 100% cpu and becomes generally slow and unstable.

How to reproduce:

1. Create two large (200000 or so elements) vectors (gyrodata.dat can be used).  
2. Open the Data Manager, and create a plugin. Select a fit plugin (Fit exponential seems to cause particularly high usage). Select two different vectors as the X and Y vectors.
3. Click Apply as New.
4. Use "top" to check CPU usage of Kst.

Cpu usage will be 90% to 100%.  
After subsequent general use, kst will often crash.

Expected Behaviour:
Cpu usage should not be 90% to 100%.
Comment 1 George Staikos 2004-06-22 20:38:40 UTC
I can't reproduce any sort of memory corruption or slowness with HEAD using the "linefit" plugin.  This indicates to me that if there are any such problems, they are most likely related to the plugin you are using.
Comment 2 Rick Chern 2004-07-13 19:03:55 UTC
I think this was fixed for 0.98.  Cannot reproduce anymore.
Comment 3 George Staikos 2004-07-13 19:07:49 UTC
On Tuesday 13 July 2004 13:03, Rick Chern wrote:
> ------- Additional Comments From rchern interchange ubc ca  2004-07-13
> 19:03 ------- I think this was fixed for 0.98.  Cannot reproduce anymore.

  Yes I fixed it.  I forgot there was a bug open about it.