Android Vulkan crash reported by Firebase Crashlytics

[aliaschoondy]

Firebase Crashlytics has reported a native crash occurring inside the Axmol Vulkan backend.

The crash is reported as:

SIGABRT
ax::rhi::vk::DriverImpl::commitIsolateSubmission()

Based on the stack trace, the crash occurs while Axmol is generating additional glyphs for a Label, causing FontAtlas to create a new page and upload texture data through the Vulkan renderer.

#00 libc.so
#1 libc.so
#2 ax::rhi::vk::DriverImpl::commitIsolateSubmission()
#3 ax::rhi::vk::TextureImpl::updateSubData()
#4 ax::Texture2D::updateData()
#5 ax::Texture2D::initWithSpec()
#6 ax::Texture2D::initWithData()
#7 ax::FontAtlas::ensureNextPage()
#8 ax::FontAtlas::addNewPage()
#9 ax::FontAtlas::prepareLetterDefinitions()
#10 ax::Label::alignText()
#11 ax::Label::updateContent()
#12 ax::Label::getContentSize()

[aliaschoondy]

games.spearmint.matchinggame_issue_15b4a0a44143fbb917d46303e6e125c8_crash_session_6a18a00f02b6000117f323646090ef77_DNE_0_v2_stacktrace.txt

[aliaschoondy]

Firebase Crashlytics reports that all occurrences are:

• Android 14 only
• Xiaomi devices only

We are using:

cpp setVulkanMinAndroidApiLevel(33);

and have not observed this crash on Android 13 devices so far.

This may indicate a Xiaomi Android 14 Vulkan driver-specific issue.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.