Crash reports collection Q1 2026
-
On SA :
But with almost 20 GB left on my Watch, it does not gives credit to your assumption
-
@sky-runner Interesting that your crashes (if I read it correctly) happen before you even start the activity?
No, what I described is a crash during activity. I first start activity, then change the S+ guide while the activity is ongoing. That is supported. And, as I said, changing S+ app or guide doesn’t crash the watch on its own unless there is also on-route navigation in progress.
-
@Gilles-D. said:
But with almost 20 GB left on my Watch, it does not gives credit to your assumption
You confuse storage and memory - these are two distinctly different things. The watch has 32 GiB of storage but only 32 MiB of memory plus a few more MiB on the SoC. But anyway, I don’t think this is a memory issue. This to me seems like a race condition - software developers will understand what I mean. A race condition is when two concurrent CPU threads race each other when one is trying to mutate or delete some resources in a conflicting way, which may lead to an unexpected result. This is more likely in a multi-core CPU. These issues are notoriously difficult to reproduce and debug. They may be happening only one time out of thousand or one time out of million.
-
@sky-runner I second this. In my case it happend 3 times over 18 months or so.
Problem with those race conditions is that there is seldom something you can do to avoid them - on the user side.
-
My suunto vertical 1 crashed last weekend while manipulating suunto plus app.
Today crashed again while zooming out during my stand paddle activity (no Suunto app enabled) I sent the logs today.
-
I’ve had the same issue with my Suunto 9 Peak Pro - happening mid workout and at the START screen.
I’ve contacted support but heard nothing back yet.
I suspect the 9PP shares a similar code base to the Vertical 1.
Let me know how I can send over diagnostics - I’m a developer so familiar with application support diagnostics.
Martin
-
-
Offline
2b2bff
SILVER MEMBERS
about 17 hours ago@Woodster said:
Let me know how I can send over diagnostics
It is explained in the opening post of the thread?Race S
Yes it’s in there ta buddy - sent Suunto account details via chat.
For me the freezing issue is very likely a faulty garbage-collection issue with a SuuntoPlus app I wrote leading to RAM pressure, can easily reproduce and send logs over so that a firmware update can isolate any app issues from the actual watch.
-
Had a crash during my run today, using a Race 2. It crashed at just after 2Km into the run.
I had 3 S+ apps enabled (Cadence coach, ZoneSense and Running Economy) and was using a Polar H10 belt. Everything else were standard (no nav, battery on performance, feeling on, no music controls, etc).When I realise the watch had crashed and restarted, I’ve started a new activity to continue my run. However, this time I unselected the ZoneSense app, while keeping the other 2 S+ apps and the HR belt. The remaining 10.4Km went well, no problems.
Hope this gets sorted soon by the team.
-
@jjorgemoura try to disable ZoneSense from your S+ apps. It seems it helps me with my Race S.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login