Related
Options

Corrupt Segment - duplicate names

Ɛpsilon
over 3 years ago

I seem to have a corrupt segment on my watch (shows a silly distance/time) and the watch crashes if you try to play with it - I suspect its because (after trial and error going through them) its because it's a duplicate named segment. The two segments are third party (I didn't create them, they're from runs I've done) and so I cant remove them or stop them syncing. So far it seems harmless in that if I dont mess with it, it doesn't impact me - has anyone else seen this?

(It's a Garmin, not Strava, segment btw)

  • +1 over 3 years ago

    I've seen exactly this issue and reported it Garmin Support. I had two local segments named the same. On the watch they get mixed because segments on the watch get stored as FIT files which names are derived from segment names. So, basically, if you had two segments with the same name, only one of them would get stored on the watch, the other one is overwritten. But it is worse than that because the watch seems to index segment start positions, and if there were segments with duplicating names it could get the wrong one.

     The result of that bug is that segments with duplicating names get mixed - start point from one segment and the track from another. If you start one segment the watch want to continue tracking and finish the another of the two dulicating segments. 

  • 0 over 3 years ago in reply to silentvoyager

    Seems a simple fix - add a unique ID to the filename :) ... Logged to the bug team, here's hoping :)