Acknowledged
CIQQA-3775

drawBitmap2() crash

Hi.

I encounter some issue about using drawBitmap2() too. It seems crash happens especialy on F8 amoled.

I tried both drawable.xml config without succes :

<bitmap id="alarm_0" filename="Icons\ALARM_0.png" packingFormat="png" />

<bitmap id="alarm_0" filename="Icons\ALARM_0.png" packingFormat="png" automaticPalette="false"/>

The drawBitmap2() call :

dc.drawBitmap2(posX, posY, part, {
:tintColor => (parts[i].color != null ? parts[i].color : colors[:iconColor]) as Number,
:transform => scale
});
The log trace :
Error: Unhandled Exception
Part-Number: 006-B4536-00
Firmware-Version: '20.24'
Language-Code: eng
ConnectIQ-Version: 5.2.0
Stack:
- pc: 0x30002293
Native: false
- pc: 0x100048ae
- pc: 0x100042cf
- pc: 0x10003b44
- pc: 0x10003bed
- pc: 0x10003c82
- pc: 0x10001eb7
- pc: 0x10001b02
- pc: 0x30004f89
Native: false
- pc: 0x30005063
Native: false
- pc: 0x1000bf46
---

any idee?

Bastos65
Parents
  • in reply to flocsy🤠

    Thanks for the comment. I agree that try/catch is useful in many cases, especially when the issue is a regular Monkey C exception (null values, bad indexes, etc.).

    In my case it looks more like a native/firmware-side crash on the Fenix 8 (AMOLED). The stack trace doesn’t point to a handled Monkey C exception, and the app just terminates, so I’m not sure try/catch would actually catch anything here.

    Also, the crash only happens on the real device, not in the simulator, which makes me suspect a device-specific rendering path / firmware bug (likely around drawBitmap2()).

Comment
  • in reply to flocsy🤠

    Thanks for the comment. I agree that try/catch is useful in many cases, especially when the issue is a regular Monkey C exception (null values, bad indexes, etc.).

    In my case it looks more like a native/firmware-side crash on the Fenix 8 (AMOLED). The stack trace doesn’t point to a handled Monkey C exception, and the app just terminates, so I’m not sure try/catch would actually catch anything here.

    Also, the crash only happens on the real device, not in the simulator, which makes me suspect a device-specific rendering path / firmware bug (likely around drawBitmap2()).

Children
No Data