Debug Logging not working on ForeRunner 935

Not sure many production CIQ apps do logging (println, etc).  None of mine do.  So trying it with other apps might not tell you anything.

Fair enough. My thinking is that if it prints something it tells me it's a problem with my app, but not the converse, given what you say.

Dresbo said:

Fair enough. My thinking is that if it prints something it tells me it's a problem with my app, but not the converse, given what you say.

Not to state the obvious, but you could build a super tiny device app, widget or data field that does nothing but call System.println() when it starts up, and see if you get the same results with that user.

I tried creating a small app to test logging and it worked just fine, so it's something to do with my app. I'm going to strip out most of the code and see if it still exhibits this strange behaviour.

How tight on memory are you with the full app? Check in the sim, and under view memory, what's the peak?

It's pretty tight when everything is loaded, but it logs when it starts up and at that point it's around 95k out of 128, so there's still space.  Running it's nearer 115k, but I don't let it run out.

You're looking at peak memory and not current, correct?  BTY, you'll see a increase in peak if you use app settings while your app is running.

My line of thinking is that if you're close to the max, the sys.println calls might not have enough memory to do their thing.

It's been a while, but I've had no problem logging on a fenix 5, which is basically the same as a 935.

But when a println() call fails due to running out of memory, the app typically crashes, as opposed to failing silently.

Like I said, it was just a guess, and could depend on what runs out of memory.