https://bugs.kde.org/show_bug.cgi?id=361646
Akarsh Simha <akarsh.si...@kdemail.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |akarsh.si...@kdemail.net
--- Comment #3 from Akarsh Simha <akarsh.si...@kdemail.net> ---
Dear Rob
I'm sorry that this is happening. Such an issue is rather hard to debug, unless
we can find out what KStars is doing / spending time on. If we can isolate the
problem a bit more and find what can be disabled to prevent this, we could
introduce a patch that has timers to further trace the issue.
The other option, if it works is to run KStars on valgrind with callgrind, keep
the machinery off until the problem begins, and then turn on the machinery to
investigate what KStars is spending most of its time.
I didn't read this anywhere in your post, but have you tried turning off the
simulation clock? Does that have any impact? I had a similar issue a while ago
with simulation clock running. If the simulation clock being off ameliorates
the problem, a temporary solution would be to keep it off and update the time
once every minute using a DBus command like this:
while true; do qdbus org.kde.kstars /KStars org.kde.kstars.setTimeToNow; sleep
55; done;
--
You are receiving this mail because:
You are watching all bug changes.
