• Replies 5 replies
  • Subscribers 18 subscribers
  • Views 1227 views
  • Users 0 members are here
Options
Related

Simulator crashes constantly

Former Member
Former Member
I am running a heavier app which uses a variable array to track positioning. It doesn't get to out of memory, but after a while (a few minutes) the simulator just hangs and eventually the O/S shuts it down. The app varies in memory usage between 50-90k where 128 or so is available.

The app can work on the actual watch for hours - it never crashed the watch or crashed on the watch.
  • With bug reports, you want to note the version of the SDK, the OS you're running on, etc (the environment), and maybe email a .zip of the project. (see the sticky at the top of this forum) If you're using simulated data or playing back a .fit might also come into play.

    If possible, see if you can reproduce it with something smaller - I try to start with one of the SDK samples, and add a bit of code to reproduce the bug for example, as that can make finding it/fixing it a bit easier for Garmin.
  • Former Member
    Former Member
    Latest SDK 2.4.5 on Windows 10. Using simulated data that comes with the package.

    Best thing would be if the simulator had some log, then I could attach it (maybe a future version :) ).

    That's the best I can do.

    The simulator was always (I think) dying if you leave it running for long enough.
  • You may want to zip up your project and send it to garmin, as it might be something unique to it.

    On win10, with the 3.0.0b1 sdk, using simulated data, I did a couple of test runs of about 2 hrs each yesterday, and no problem. The app itself is about 90k.

    One thing you could try though is to clear out the sim's temp directory. On Windows, that should be %tmp%/garmin

    update: I had another test to run this morning, but I switched to the 2.4.5 SDK, and it again ran fine for a couple hours.
    So, it's not the sdk version.
  • Former Member
    Former Member
    It looks like it dies most often when you re-run the app after the previous one was running for a while. I will try the temp directory suggestion. thanks.
  • If you have one running in the sim, terminate that app before you run it again and see if that avoids the problem. (however you end the app on the watch, or with Ctrl+a in the sim)