Acknowledged

Problems with Custom Fonts - Graphics Pool - on Edge 1050 only

Crashes occur on using custom fonts, but only on device Edge 1050, and it happens every now and then. (Hardly to reproduce on any 1050 device...)
It is definitely not a code error, because - as I said - it happens now and then, but only with Edge 1050:

Error Name: Symbol Not Found Error
Occurrences: 1
First Occurrence: 2025-02-14
Last Occurrence: 2025-02-14
Devices:
Edge® 1050: 12.16
App Versions: 1.3.1
Languages: dut
Backtrace:
CleanMapFieldsView.onUpdate:3349

Line 3349 is the first appearance of using the custom font myTINY_T in onUpdate(dc) :
dc.drawText( 10, 5, myTINY_T, "GPS", textCenter);


...and this font is loaded in initialize() without error:
myTINY_T = WatchUi.loadResource(Rez.Fonts.id_font_myTINY_T5);


Despite the stack trace, it's probably not literally crashing on the actual call to dc.drawText(), but likely in CIQ API code within drawText (or called by drawText).
What seems to be happening: loadResource returns a FontReference on CIQ 4+ devices, which is actually a reference to the graphics pool, and there's possibly a bug in edge1050 which causes an access of a valid graphics pool reference to crash. (i.e. perhaps the font resource has been automatically unloaded from the graphics pool, but the graphics pool is unable to reload it when necessary)

  • Thank you for investigating.

    The problem is: me, too, cannot cause a crash om my Edge 1050!
    As I said in my opening post: 

    it happens every now and then. (Hardly to reproduce on any 1050 device...)

    And I documented, what I do:

    the font is loaded in initialize() without error:
    myTINY_T = WatchUi.loadResource(Rez.Fonts.id_font_myTINY_T5);


    Crash in line 3349 is the first appearance of using the custom font myTINY_T in onUpdate(dc) :
    dc.drawText( 10, 5, myTINY_T, "GPS", textCenter);

    For hundrets of user with a Edge 1050, it works flawlessly (me included).

  • Would you be able to share a CIQ project that causes this issue? I've been testing with our own project that implements custom fonts, but have been unable to cause a crash. I suspect you may be doing something a bit differently.