mapbox / mapbox/mapbox-maps-ios

MapboxCoreMaps Crashes

Open
#2,052 10 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auto-triaged bug :beetle:
Dominant language
Swift
Stars
601
Forks
196
PR merge metrics
No merged PRs in 30d

Description

Environment

  • Xcode version: 14.3.1
  • iOS version: 17.0.3, 17.1.0, 16.3.1, 16.0.0
  • Devices affected: iPhone 13 Pro, iPhone 14, iPhone 13, iPhone 14 Pro Max, iPhone 11 etc.
  • Maps SDK Version: 10.16.1

Observed behavior and steps to reproduce

Crash from MapboxCoreMaps with message

Pure virtual function called!

pure-virtual-function-stack-trace.txt

We also see in crashlytics a lot of crashes from MapboxCoreMaps with messages

malloc: Heap corruption detected, free list is damaged at 0x280bf9200 *** Incorrect guard value: 10749975056

and

malloc: Incorrect checksum for freed object 0x116208c00: probably modified after being freed. Corrupt value: 0x1160c5600

with different stack traces. Example:
incorrect-checksum-stack-trace.txt

Expected behavior

no crashes

Notes / preliminary analysis

We migrated from Mapbox v6. At the time, around 10% of users, who updated or downloaded brand new version, experience some of these crashes.
Unfortunately, I was unable to reproduce it on any of my devices.

It looks like all the crashes are about accessing released objects memory somewhere inside MapboxCoreMaps

I will be grateful for any help here

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 by reviewing pure-virtual-function-stack-trace.txt and incorrect-checksum-stack-trace.txt, then inspect the MapboxCoreMaps call paths shown in those traces. Compare the different crash stacks and the reported iOS and SDK versions. Done means identifying and fixing the released-object or memory-corruption cause so the reported crashes no longer occur.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.