Ticket Created
over 5 years ago

WERETECH-9597

Garmin 530 Maptrackview Device crash

Hi

When trying to draw on top of a mapview or maptrackview the device crashes and restarts. Works perfectly on the simulator but not on the actual device.

Error log below.

Any ideas on the issue?

[
{
"unit_id":"3314263625",
"product_name":"Edge 530",
"software_part_number":"006-B3121-00",
"ms_since_epoch":1598646976000,
"system_version":"6.00",
"build_type":"PRODUCTION",
"backtrace":"
Function Address: 0x6070AFC8
   Call Address at Function: 0x6070BEB4

Function Address: 0x60709F84
   Call Address at Function: 0x6070A0B6

Function Address: 0x604AE620
   Call Address at Function: 0x604AE7D4

Function Address: 0x604B15A0
   Call Address at Function: 0x604B1648

Function Address: 0x604B16C2
   Call Address at Function: 0x604B193C

Function Address: 0x604B2F54
   Call Address at Function: 0x604B2F66

Function Address: 0x60490ED4
   Call Address at Function: 0x60490F90

Function Address: 0x604AAC1C
   Call Address at Function: 0x604AADB4

Function Address: 0x60431FFC
   Call Address at Function: 0x604320A8

Function Address: 0x60222B9C
   Call Address at Function: 0x60222BBC

Function Address: 0x60250158
   Call Address at Function: 0x602501AC

Function Address: 0x6024FFA8
   Call Address at Function: 0x60250030

Function Address: 0x600E71B0
   Call Address at Function: 0x600E7CEA

Function Address: 0x60431E74
   Call Address at Function: 0x60431E86

Function Address: 0x609BCE5A
   Call Address at Function: 0x609BD0CA

Function Address: 0x6043144C
   Call Address at Function: 0x60431488

Function Address: 0x60430D18
   Call Address at Function: 0x60430D3A

Function Address: 0x60431708
   Call Address at Function: 0x6043179E

Function Address: 0x60214000
   Call Address at Function: 0x6021407C

",
"error_cause":"RTL Trap",
"proprietary_info":{
    "Commit ID":"2d0bc753c0b194019d3d731404ccbdc0cb6f883c",
    "Time":"2020-8-28 22:36:16",
    "Project Specific":"2020-8-28 22:36:16",
    "CDP_LOG":"605CE741,6044BE99,605B5C5D,6020894D,605CDADD,6020894D,601C6919,601C6919,605B5791,",
    "RTL Error Number":"6E5D8024",
    "Error Message":"00000000,FFFFFF00,00000018,0000F7EB,D08FBF80,00000000,00000102,0000003F,0000007A,0000007A,60B87284,61EDB43C,61EDB48C,61EDB3E8,6070BAD4,6070BEB4,2000001F",
    "Task Name":"CDP main",
    "Saved SP":"61EDB3E8",
    "Saved LR":"6070BAD4",
    "Saved PC":"6070BEB4",
    "R[0]":"00000000",
    "R[1]":"FFFFFF00",
    "R[2]":"00000018",
    "R[3]":"0000F7EB",
    "R[4]":"D08FBF80",
    "R[5]":"00000000",
    "R[6]":"00000102",
    "R[7]":"0000003F",
    "R[8]":"0000007A",
    "R[9]":"0000007A",
    "R[10]":"60B87284",
    "R[11]":"61EDB43C",
    "R[12]":"61EDB48C",
    "R[13]":"61EDB3E8",
    "R[14]":"6070BAD4",
    "R[15]":"6070BEB4",
    "cpsr":"2000001F"
    }

}
]

shane.elliott
Parents
  • over 5 years ago in reply to shane.elliott

    Something not related to the crash.  In the sim you don't see this, but on the actual device, the map scale is displayed at the bottom right corner, and you're covering that.  On watches, the scale is displayed at the bottom center.  Also, at night, there can be a black background to the map instead of a white one.

    Are you using Ui.requestUpdate() to update the MapTrackView, or are you letting the view take care of itself?

Comment
  • over 5 years ago in reply to shane.elliott

    Something not related to the crash.  In the sim you don't see this, but on the actual device, the map scale is displayed at the bottom right corner, and you're covering that.  On watches, the scale is displayed at the bottom center.  Also, at night, there can be a black background to the map instead of a white one.

    Are you using Ui.requestUpdate() to update the MapTrackView, or are you letting the view take care of itself?

Children
  • over 5 years ago in reply to jim_m_58

    I also tried moving the mapview.onUpdate() to after the dc.draw call but no difference for me. Works fine on the sim but crashes on the 530.

  • over 5 years ago in reply to jim_m_58

    That wasn't it, as I still see the crash at times - like I did before

  • over 5 years ago in reply to shane.elliott

    I think I found it in my own app.  I tracked down the crash to a dc.drawText() call, while doing everything else I normally do in onUpdate() like markers..

    So then I looked at reproducing it in the MapSample in the SDK.  It's always good to provide code to reproduce something in a bug report, and I'll often start with a sample.  Made one change, doing a dc.drawText().

    And it worked fine.  So I tried to figure out what was different from my app.

    In the MapSample, if I comment out the line

    MapView.onUpdate(dc);

    I got the crash

    I looked at my code, and for some reason had it comment out there too.  I added it back in, and no crash in my app!

    Are you making that call?

  • over 5 years ago in reply to jim_m_58

    Ok so tried running the app with adding a return to onUpdate() and leaving the maptrackview to update itself with no problems. I also added a println() to onUpdate() and updates are maybe slightly more than once per second but does not seem to be an issue. Everything works well until add any kind of draw to onUpdate() even a static dc.drawText(). Will probably just have to work around not have any data on the mapview for now but not ideal.  

  • over 5 years ago in reply to shane.elliott

    Better yet, since this sounds like this is your first app using MapTrackView, in onUpdate() for the MapTrackView, do a return as the first line, so bypass your own code in onUpdate.  Then sideload it to the 530, and just see how things look without you doing anything.  That will show the scale, what the view itself does, etc,  The sim isn't that great with maps vs the actual device, and I do most of my testing of maps on an actual device..