0

Force Quit on Observing Lists

Jean-Claude JESIOR

May 04, 2018 05:23

None

Follow

This is a very subtle bug which has to do with the Observing Lists

I found it on multiple occasions over a period of several days on two computers.

 

What one should do to find this bug is :

Select an observing list

Navigate through the list with the Up and Down keys

Highlight the objects of the list and Select Next Object

Click on an object of the chart which doesn’t belong to the highlighted list

Return to the Observing List and select an object

At one of these stages, the popup Show List at the bottom of the chart will not respond anymore and the only way to get out is a Force Quit.

SkySafari 6 Pro on macOS High Sierra

• Facebook
• Twitter
• LinkedIn

4 comments

• 0
  
  Bill Tschumy May 04, 2018 14:18

  Jean-Claude,

  I spent about 5 minutes trying to reproduce your problem.  No luck.  You must be doing something subtly different from what I'm doing.  Could you try to find a reproducible case of this?

• 0
  
  Jean-Claude JESIOR May 04, 2018 14:51

  Well Bill, you don't try hard enough : I just got at least 3-4 freezes (problems) within a quarter of an hour.

  But this is very difficult for me to define the circumstances of these freezes.

  Just open an observing list, navigate with the arrows, highlight the objects, click on the chart , select Next Object (dlg saying it's not in the list), go back to an object of the observing list, click on Next Object, etc... 

  Keep playing and at one stage you'll see something going wrong like the popup menu at the bottom of the chart refuses to close, or you cannot select an object in the observing list, or ....

• 0
  
  Jean-Claude JESIOR May 04, 2018 14:54

  Here is a screenshot of my frozen SkySafari with the popup menu refusing to disappear

  Hope this helps.

• 0
  
  Bill Tschumy May 04, 2018 15:39

  I really need a sequence of steps to reproduce.

  Barring that, you could try launching the Console.app app and filter on "SkySafari".  See if an error is written to the console when this happens.  That might give me enough info to fix this.