-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Crash targeting 4K external display — GL_INVALID_VALUE #13703
Comments
@kkaefer do we clamp the frame buffer size? |
#13701 (review) notes that this crash occurs when targeting a 4K Apple TV as an external display. What’s interesting to me is that I don’t get a crash when a 4K Apple TV (simulator) is the primary display for the tvOS map SDK, which is virtually identical to the iOS map SDK: #9319. |
FYI I also had this problem on a screen that was < 4k, but this was with an earlier Apple TV (3rd gen). EDIT: Specific device/tv info:
|
This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
The external display support added to iosapp in #13701 works well in the simulator for external displays at 640×480, 720×480, 1,024×768, 1,280×720 (720p), and 1,920×1,080 (1080p) resolutions, but mbgl immediately crashes when displaying the map view on a 3,840×2,160 (4K) display.
The stack trace isn’t particularly enlightening, but it is worth noting that there are four worker threads at the time of the crash:
The console output is also interesting:
/cc @mapbox/maps-ios @mapbox/gl-core
The text was updated successfully, but these errors were encountered: