mapbox / mapbox/mapbox-maps-android

In Android,how to solve this crash in MapboxRenderThread

Open
#2,535 1 comment 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auto-triaged bug :beetle:
Dominant language
Kotlin
Stars
578
Forks
161
PR merge metrics
No merged PRs in 30d

Description

## Environment

- Android OS version: No specific version required.
- Devices affected: No specific devices required.
- Maps SDK Version: com.mapbox.maps:android:11.8.0

My app, which is related to maps, frequently encounters crashes, and I have collected similar crash information.
Could you please advise on how to locate and resolve these issues?

```
#00 pc 000000000019882c /vendor/lib64/egl/libGLESv2_adreno.so [arm64-v8a::c8ff05ee7770eabb902f5e18c4c04e0a] #01 pc 00000000007c890c /data/app/~~KgsUuxUik8_0VW0C84H-6A==/com.chinasiwei.offroadearth-B7bDCYMIArr_Rlvuu8n0Uw==/lib/arm64/libmapbox-maps.so [arm64-v8a::e42c4c5803359c8c3ee58ce359c23904]
#02 pc 00000000005294b0 /data/app/~~KgsUuxUik8_0VW0C84H-6A==/com.chinasiwei.offroadearth-B7bDCYMIArr_Rlvuu8n0Uw==/lib/arm64/libmapbox-maps.so [arm64-v8a::e42c4c5803359c8c3ee58ce359c23904]
#03 pc 00000000005a08b8 /data/app/~~KgsUuxUik8_0VW0C84H-6A==/com.chinasiwei.offroadearth-B7bDCYMIArr_Rlvuu8n0Uw==/lib/arm64/libmapbox-maps.so [arm64-v8a::e42c4c5803359c8c3ee58ce359c23904]
#04 pc 00000000005b1744 /data/app/~~KgsUuxUik8_0VW0C84H-6A==/com.chinasiwei.offroadearth-B7bDCYMIArr_Rlvuu8n0Uw==/lib/arm64/libmapbox-maps.so [arm64-v8a::e42c4c5803359c8c3ee58ce359c23904]
#05 pc 00000000005a300c /data/app/~~KgsUuxUik8_0VW0C84H-6A==/com.chinasiwei.offroadearth-B7bDCYMIArr_Rlvuu8n0Uw==/lib/arm64/libmapbox-maps.so [arm64-v8a::e42c4c5803359c8c3ee58ce359c23904]
#06 pc 00000000005a1ab8 /data/app/~~KgsUuxUik8_0VW0C84H-6A==/com.chinasiwei.offroadearth-B7bDCYMIArr_Rlvuu8n0Uw==/lib/arm64/libmapbox-maps.so [arm64-v8a::e42c4c5803359c8c3ee58ce359c23904]
#07 pc 000000000044f168 /data/app/~~KgsUuxUik8_0VW0C84H-6A==/com.chinasiwei.offroadearth-B7bDCYMIArr_Rlvuu8n0Uw==/lib/arm64/libmapbox-maps.so [arm64-v8a::e42c4c5803359c8c3ee58ce359c23904]
#08 pc 00000000004481bc /data/app/~~KgsUuxUik8_0VW0C84H-6A==/com.chinasiwei.offroadearth-B7bDCYMIArr_Rlvuu8n0Uw==/lib/arm64/libmapbox-maps.so [arm64-v8a::e42c4c5803359c8c3ee58ce359c23904]
#09 pc 00000000008545e8 /data/app/~~KgsUuxUik8_0VW0C84H-6A==/com.chinasiwei.offroadearth-B7bDCYMIArr_Rlvuu8n0Uw==/lib/arm64/libmapbox-maps.so [arm64-v8a::e42c4c5803359c8c3ee58ce359c23904]
#10 pc 0000000000045dc4 /data/app/~~KgsUuxUik8_0VW0C84H-6A==/com.chinasiwei.offroadearth-B7bDCYMIArr_Rlvuu8n0Uw==/oat/arm64/base.odex [arm64-v8a::eb4fbd440ad57f5912ce1a772bbf27ae]
java:
com.mapbox.maps.NativeMapImpl.render(SourceFile:3)
com.mapbox.maps.renderer.MapboxRenderer.render(SourceFile:5)
com.mapbox.maps.renderer.MapboxRenderThread.draw(SourceFile:100)
com.mapbox.maps.renderer.MapboxRenderThread.doFrame(SourceFile:143)
android.view.Choreographer$CallbackRecord.run(Choreographer.java:1503)
android.view.Choreographer$CallbackRecord.run(Choreographer.java:1513)
android.view.Choreographer.doCallbacks(Choreographer.java:1128)
android.view.Choreographer.doFrame(Choreographer.java:1037)
android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1481)
android.os.Handler.handleCallback(Handler.java:942)
android.os.Handler.dispatchMessage(Handler.java:99)
android.os.Looper.loopOnce(Looper.java:211) android.os.Looper.loop(Looper.java:300)
android.os.HandlerThread.run(HandlerThread.java:67)
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported stack frames and the Android entry points NativeMapImpl.render, MapboxRenderer.render, and MapboxRenderThread.draw/doFrame. Check whether the crash can be reproduced with com.mapbox.maps:android:11.8.0 and determine the affected rendering path. Done means identifying a supported cause and documenting or implementing a verified fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
computer-graphics, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.