Bug 423137 - Spinning Beachball during Alignment Capture
Summary: Spinning Beachball during Alignment Capture
Status: RESOLVED WORKSFORME
Alias: None
Product: kstars
Classification: Applications
Component: general (other bugs)
Version First Reported In: 3.4.2
Platform: Other macOS
: NOR grave
Target Milestone: ---
Assignee: Jasem Mutlaq
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-18 07:53 UTC by MountainAirCA
Modified: 2021-01-28 04:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Spinning beachball log (90.00 KB, text/plain)
2020-07-12 20:41 UTC, MountainAirCA
Details

Note You need to log in before you can comment on or make changes to this bug.
Description MountainAirCA 2020-06-18 07:53:26 UTC
SUMMARY

When capturing images during the polar alignment routine, the Mac version of KStars connected to StellarMate sees long delays and a spinning beackball cursor.  This can often delay an image 30 seconds, making most short-duration operations in KStars almost unbearably long.   This may happen in other modules that use the camera, but I tend to not get past alignment when it happens.  Quitting and restarting KStars and StellarMate has no effect, nor does rebooting the Mac.

Note: Could this be related to the Wi-Fi network at my dark sky site not having an Internet connection? Maybe that’s why I never seem to experience this at home.  This did happen to me once before, but it somehow went away on its own. Now it’s back.

Unfortunately I enabled logging but missed writing it to a file. I will try to capture a log later tonight.

STEPS TO REPRODUCE
1. Launch KStars on Mac
2. Start equipment profile that points to StellarMate
3. Enter alignment module
4. Begin polar alignment

OBSERVED RESULT

There is a long delay and a “spinning beachball of death” before each captured frame.

EXPECTED RESULT

No delay.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 10.15.5
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 MountainAirCA 2020-06-22 05:52:35 UTC
I was able to capture logs of the spinning beachball capture problem, but I couldn't send them that night because I was in the middle of the desert with no Internet access.

Today I fired up KStars, opened the logs directory... and the only logs I had were from today.  Does KStarts automatically delete logs for previous days?  If so, can this be configurable with a 10-day default?
Comment 2 MountainAirCA 2020-07-08 05:54:35 UTC
For what it's worth, the last time I was at the same dark-sky site with the same equipment and the same network gear, this beachball behavior on each image capture did not occur.  There were no other changes in running software, etc.  Unfortunately these intermittent issues are the worst to track down, but if it happens again I will capture the log.
Comment 3 MountainAirCA 2020-07-12 20:41:20 UTC
Created attachment 130071 [details]
Spinning beachball log

Spinnig beachball delay between exposures on Mac.
Comment 4 MountainAirCA 2020-07-12 20:44:02 UTC
Hi Jasem, I was able to reproduce the spinning beachball problem (log attached), but I'm unsure why this happens some nights and not others.  I can see a roughly ~30s delay between exposures in the log.  This is perhaps not a great example because it happened during the polar alignment wizard, but I'm pretty sure it was not a plate-solving delay.  Thanks for looking into it!
Comment 5 Jasem Mutlaq 2020-12-14 16:50:27 UTC
Happens also in 3.5.0?
Comment 6 Bug Janitor Service 2020-12-29 04:34:25 UTC
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!
Comment 7 MountainAirCA 2020-12-29 21:57:05 UTC
I am not sure if this still occurs, as I stopped using remote connections from one Kstars/Ekos to another.  However, due to another issue with memory use on RPi-4 and full-frame cameras, I will need to test remote connections the next time I am at my dark-sky site.

I will report back at that time.
Comment 8 Bug Janitor Service 2021-01-13 04:33:47 UTC
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!
Comment 9 Bug Janitor Service 2021-01-28 04:33:15 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!