You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Constantly feed updated location to simulate navigation scenarios
Pinch to adjust the pitch level to around 50 degrees
Observe CPU spike to ~400%
App crashes with Metal vertex buffer error
Expected behavior
The map should handle high pitch ranges during navigation without performance degradation or crashes.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform information (please complete the following information):
OS: [iOS]
Platform [iOS]
Version [18.1]
Additional context
The error suggests a vertex buffer at index 1 is being accessed but doesn't exist, indicating a potential issue with buffer management in the Metal rendering pipeline.
sorry it was a mistake at my side I meant MetalTools
the app is using MapLibre SwiftUI DSL](https://github.com/maplibre/swiftui-dsl) and Ferrostar navigation
To reproduce it:
you can use Ferrostar demo https://github.com/stadiamaps/ferrostar
start navigation and change the pitch value to its max. there is huge performance regression in this case.
Describe the bug
The app crashes during navigation when using MapLibre Native iOS with specific conditions:
The crash occurs in:
To Reproduce
Steps to Reproduce
Expected behavior
The map should handle high pitch ranges during navigation without performance degradation or crashes.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform information (please complete the following information):
Additional context
The error suggests a vertex buffer at index 1 is being accessed but doesn't exist, indicating a potential issue with buffer management in the Metal rendering pipeline.
Stacktrace
The text was updated successfully, but these errors were encountered: