• Replies 14 replies
  • Subscribers 18 subscribers
  • Views 2986 views
  • Users 0 members are here
Options
Related

Lots of Invalid errors reported in ERA points to font resource load line

trudelta

I am finding a lot of occurrences of and Invalid error reported in ERA as below

Error Name: Invalid Value
Occurrences: 69
First Occurrence: 2022-08-20
Last Occurrence: 2022-08-22
Devices:
fēnix® 6S Pro / 6S Sapphire / 6S Pro Solar / 6S Pro Dual Power: 22.10
fēnix® 6 Pro / 6 Sapphire / 6 Pro Solar / 6 Pro Dual Power / quatix® 6: 22.10
fēnix® 5 Plus: 18.00
 epixTm (Gen 2) / quatix® 7 Sapphire: 8.37, 9.33
vívoactive® 4: 6.90
 fēnix® 7X / tactix® 7 / quatix® 7X Solar / EnduroTm 2: 8.37
fēnix® 7 / quatix® 7: 8.37
 DescentTm Mk2 / DescentTm Mk2i: 14.10
Forerunner® 255 Music: 11.12
fēnix® 6 / 6 Solar / 6 Dual Power: 22.10
Forerunner® 255: 11.12
fēnix® 6X Pro / 6X Sapphire / 6X Pro Solar / tactix® Delta Sapphire / Delta Solar / Delta Solar - Ballistics Edition / quatix® 6X / 6X Solar / 6X Dual Power: 22.10
fēnix® 6S / 6S Solar / 6S Dual Power: 22.10
fēnix® 5S Plus: 17.10
fēnix® 6X Pro / 6X Sapphire / 6X Pro Solar / tactix® Delta Sapphire / Delta Solar / Delta Solar - Ballistics Edition / quatix® 6X / 6X Solar / 6X Dual Power: 22.10
 epixTm (Gen 2) / quatix® 7 Sapphire: 8.37
MARQ® Aviator: 22.10
fēnix® 5X Plus: 18.00
Forerunner® 955 / Solar: 12.20, 11.12
Forerunner® 245 Music: 11.10
 fēnix® 7X / tactix® 7 / quatix® 7X Solar / EnduroTm 2: 8.37
MARQ® Athlete: 22.10
MARQ® Captain / MARQ® Captain: American Magic Edition: 22.10
 fēnix® 7X / tactix® 7 / quatix® 7X Solar / EnduroTm 2: 8.37, 8.39
Forerunner® 255s Music: 11.12
App Versions: 1.2.1
Languages: ces, chs, cht, dan, deu, dut, eng, fre, heb, ita, jpn, kor, pol, rus, slo, spa, swe
Backtrace:
Background.draw:33

-------

The offending line is 

var faceFont = Toybox.WatchUi.loadResource(Rez.Fonts.Num);
 
or one of the lines immediately following this line.  The resource is valid as far as I can see.  Everything works fine in the simulator with no warnings or errors, and there is plenty of memory margin.  For example, on a watch with 92k available for the watchface, peak memory use is <56k and reported running memory use is <46k.   Usually the issue with this operation is out of memory but I think this is not the case.  
Has anyone else seen this and have any comments?