https://bugs.kde.org/show_bug.cgi?id=361646

            Bug ID: 361646
           Summary: KStars hogs CPU until unusable
           Product: kstars
           Version: unspecified
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: mutla...@ikarustech.com
          Reporter: kst...@meades.org

I'm running KStars (v.2.5.0 with KDE Frameworks 5.9.0) as a client on Xubuntu
(15.10) on a Dell Latitude D830 laptop.  When KStars is first launched the
kstars process consumes ~15% (according to 'top') and KStars is very usable. 
However, after about 10 minutes of normal operation (doing nothing other than
scrolling around the KStars sky and looking at stuff), KStars starts hogging
CPU, getting to between 60% and 80%; the lag makes it pretty much unusable at
the point.  The laptop has Intel Core 2 Duo T7100/1.8 GHz processors and 4
Gbytes RAM. The RAM is never more than half used, the swap file is unused. I am
running the correct NVIDIA drivers for the graphics card.

When it gets into this state only a reboot will fix it.  If I just close and
restart KStars it takes a very long time to load and the kstars process still
consumes between 60% and 80% of CPU when just sitting there idle.

I'm very happy if there's a workaround or some tuning required for this: I
really want to use KStars!

Reproducible: Always

Steps to Reproduce:
1.  Start kstars.
2.  Scroll around looking at the sky for more than 10 minutes.
3. Wait for things to slow down.

Actual Results:  
The kstars process was using between %60 and %80 of CPU and the lag caused it
to be unusable.

Expected Results:  
The kstars process to consistently consume no more than 20% to 30% CPU when
idle.

The processing system has Intel Core 2 Duo T7100/1.8 GHz processors and 4
Gbytes RAM. The RAM is never more than half used, the swap file is unused. I am
running the correct NVIDIA drivers for the graphics card (nvidia-340).

My intention is to use Ekos as a client with remote Indi but the above happens
without any of that running.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to