Acknowledged
7 months ago

OLED: font resources seem to be forgotten while sleeping which leads to a crash onExitSleep

It seems that OLED watches now release fonts when sleeping and onExitSleep is called before initialize, so the app crashes when it uses fonts in the onExitSleep to update the layout. 

I get null exception while a resource is expected on this line that is called from onExitSleep.

"UnexpectedTypeException: Expected Number/Resource, given null…"

I got thousands of failure reports on this line from a variety of OLED devices. 

I do not release fonts anywhere in the code and the same line is called via initialize without problems. 

I hotfixed it by catching the exception and calling the initialize instead, but that is a huge wasting of resources and probably a battery. 

I am not aware of any documentation that the Monkey might release any resources on its own and even if it does, I'd expect it would call initialize before onExitSleep. 

Some of devices where the error occurred: 

  • Venu® 3: 8.25
  • vívoactive® 5: 8.27, 4.14
  • Forerunner® 265s: 17.26

EDIT: added an exception text

EDIT2: added devices 

myneur
Parents
  • 7 months ago in reply to _psx_

    That could be a problem as well, but does not explain why the fonts are removed from memory. 

    I consider onLayout a method to be called when a layout recalculation is needed. 

    I consider initialize the method where resources are expected to load. 

    So if Garmin decides to unload resources by its own, without any instructions to do that, I'd expect it will call initialize again. 

    I'd personally guess, that releasing the resources is a bug as well. 

Comment
  • 7 months ago in reply to _psx_

    That could be a problem as well, but does not explain why the fonts are removed from memory. 

    I consider onLayout a method to be called when a layout recalculation is needed. 

    I consider initialize the method where resources are expected to load. 

    So if Garmin decides to unload resources by its own, without any instructions to do that, I'd expect it will call initialize again. 

    I'd personally guess, that releasing the resources is a bug as well. 

Children