mapbox / mapbox/mapbox-vision-ios

Crash on MapboxVisionSafetyNative 0x105607760 mapbox::vision::CollisionPredictor::UpdateHistory

Open
#356 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

User Feedback
Dominant language
Swift
Stars
63
Forks
26
PR merge metrics
No merged PRs in 30d

Description

## Description
Crash on mapbox::vision::CollisionPredictor::UpdateHistory

## Screenshots

```
Crashed: Thread
0 MapboxVisionSafetyNative 0x105607760 mapbox::vision::CollisionPredictor::UpdateHistory(std::__1::pair const&) + 394
1 MapboxVisionSafetyNative 0x1056089ec mapbox::vision::CollisionManager::Update(mapbox::vision::VisionState const&, float, cva::CoreData const&) + 236
2 MapboxVisionSafetyNative 0x10560b474 mapbox::vision::VisionSafetyManagerImpl::OnUpdate(mapbox::vision::InternalState const&, cva::UpdateTime) + 104
3 MapboxVisionNative 0x1045c9ea8 mapbox::vision::VisionManagerImpl::UpdateInternalThread() + 324
4 MapboxVisionNative 0x1045b2d3c i.1915 + 172
5 libsystem_pthread.dylib 0x1dec7fcb0 _pthread_start + 320
6 libsystem_pthread.dylib 0x1dec88778 thread_start + 8
```

## Configuration
- Device: iPhone 11 Pro Max
- OS: iOS 14.4
- Frameworks versions (leave the ones you're using):
- MapboxVisionNative [0.14.0]
- MapboxVisionSafetyNative [0.14.0]
- MapboxVision [0.14.0]

## Additional context
Can't recreate at will, but does happen on almost every trip

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 crash stack, especially CollisionPredictor::UpdateHistory and CollisionManager::Update, using the MapboxVisionNative, MapboxVisionSafetyNative, and MapboxVision versions listed for iOS 14.4. The issue provides no source file, reproduction steps, or test; done would require identifying the cause of the recurring trip crash and demonstrating that it no longer occurs.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile-dev
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.