• Replies 12 replies
  • Subscribers 18 subscribers
  • Views 2565 views
  • Users 0 members are here
Options
Related

Simulator hanging on Mac Mojave

Alan.raceQs
The sim runs for 10-30 sec's then freezes. Appears in red ("Not responding") in Activity Monitor and requires forced stop.
Seems to be sensitive to a) how much is going on the the app and b) how much other work is going on in the Mac (screen swapping, docs updating etc)

Don't know how long it's been an issue I updated to Mojave a couple of days ago.
Eclipse Oxygen.3a, SDK 3.0.1

I'm unable to do any useful testing.

  • Thanks for the report. We'll take a look and see if we can reproduce.
  • I've seen the simulator hang pretty consistently while trying to do Run No Evil tests on 13 devices. The project would build for one of the devices, then hang before even entering my single test function (which simply iterated through device and app waypoints and logged the names and IDs to the console). And it was never the same device, although it seemed to usually be one of the ones in the middle, and not the very first one.

    The only way I was able to get through the full suite of tests was to avoid doing anything during the tests (such as switching to the console, scrolling through the output). Just basically had to walk away from the PC while the tests were running.

    Didn't seem to have the same problem just running my app (widget) normally.

    I'm on Windows 10, with CIQ SDK/plugin 3.0.4.
  • Thanks for the report. We'll take a look and see if we can reproduce.


    It’s very reassuring to see that forum posts are being monitored by Garmin. (It’s not the case with a certain competitor)
  • In order to continue development while the issue is being sorted, is there any point in reverting to an earlier SDK? Which one? I suspect the issue is with the sim but have no idea how that is packaged with the SDK.
    [UPDATE] I reverted to 2.4.9 - it seemed to be better... no hang, but it did crash after 5 mins when I was working it very hard.

    [UPDATE] I'm still getting occasional crashes and hangs with SDK 2.4.9, but I'm not certain which version of the Sim is in play - it reports a version of 99.99.99 which seems a bit odd!
    [UPDATE] the Sim in SDK 3.0.3 reports version 3.0.0 copyright 2014-2017 whereas the sim in 3.04 also reports version 3.0.0, but with a different copyright of 2014-2018. So there's a bit of a problem with the version numbering!
  • I too am having issues, and it seems like the bigger the app, the worse it gets. I'm on Windows 10, so it isn't a mac thing. First exiting the app (either exit or File > Kill) seems to help.
  • I'm experiencing this issue also, on both MacOS 10.14 and now 10.14.1. I don't think this is a time-based issue, because if I can get past the hang at the start then I can do things on my METAR/TAF widget until it randomly starts to hang.

    Is it possible this is related to the use of Timer objects, perhaps on the stopping and/or cleanup? As a test I put my widget into the first-run startup loop where I use a Timer to display a "status" circle arc moving around the outside of the screen while the widget waits for a GPS fix. So long as I don't enable "Simulate Data" the status arc continues to move indefinitely. Then when I enable "Simulate Data" and the simulator returns a GPS fix, the simulator runs for a couple more seconds while it starts the next process of retrieving data and then it hangs.

    Alternatively, could this be related to retrieving resources/data using the Communications functionality? The hanging could also be at the point I am retrieving data from an external site.

    Perhaps everyone running into this issue could comment as to whether or not they are using Timers and/or Communications functionality?

    I'm also seeing this warning in my console:
    BUILD: WARNING: d2charlie: /Users/douglas/develop/garmin/widgets/metar/source/MainMenuInputDelegate.mc:25: Unable to detect scope 'Menu' for the symbol 'initialize'.
  • For the warning, try adding

    using Toybox.WatchUi.Menu;
  • Perhaps everyone running into this issue could comment as to whether or not they are using Timers and/or Communications functionality?

    Yes, I'm using both. But I didn't observe any strong correlation between their use and the hangs. I have reverted to SDK 3.0.3 in order to proceed with development.