Created attachment 121978 [details] Screen print of KStars and Activity Monitor SUMMARY High CPU usage for KStars 3.3.3 - Averaging about 30% STEPS TO REPRODUCE 1. Run Kstars 2. Run macOS Activity Monitor 3. OBSERVED RESULT Mac gets hot and uses battery quicker than wanted. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: 10.14.5 Mojave Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Can you check with KStars v3.3.8 and report back?
Hi Jasem. Just installed and tried Kstars 3.3.8. CPU usage still seems similar to previously - in the range 30% to 80% when the window is active, Stellarium also uses a similar amount of CPU so maybe it is standard ... however Sky Safari uses significantly less CPU - around 6% when its window is active. I realise there is a lot of computing required to display objects in the night sky so I do expect to see higher cpu usage than what you would see in a more static application like MS Excel. Cheers Terry
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!
Tried to mark as 'reported' but says I have to select a comment??
I was going to open a bug on this myself. Note that the attached screen shot does not include what I would call high CPU use, but I can tell you that one of my reasons for trying to use a Mac-only astrophotography and scope control suite was to avoid the high CPU use of Windows running in VMWare. Unfortunately when moving to KStars, I had to run a 100-ft extension cord across the street to power the laptop -- and you're right, it gets hot. I will try to capture a screen shot of CPU my next time out.
I also see this issue. Mostly when images are being received as a remote client. Minimising kstars reduces the load significantly.
Hopefully this is minimized with KStars v3.5.5 as we added in a few optimizations. Please check if the KStars v3.5.5 beta has this issue.
FWIW, I haven't had high CPU issues in KStars for quite a while now. However, the last time I used it on the Mac for an actual imaging session was probably 3.5.3 (I moved to Ubuntu).
Seems alot better to me using version 3.5.5 stable. I only did a cursory check and although the CPU usage spiked soon after startup it soon settled to single digits. Seems this should be resolved and re-opened with more specific details if it reoccurs. Thanks