Android 36.1 arm64 guest crashes naming a valid Vulkan descriptor-set layout
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- android, cpp
- Domain
- computer-graphics
Research direction
Start with the standalone C++ reproducer described in the issue: create a descriptor-set layout, obtain vkSetDebugUtilsObjectNameEXT, and name the valid layout. Then investigate the guest-side vk_common_SetDebugUtilsObjectNameEXT path in vulkan.ranchu.so and compare behavior across the reported emulator versions. Done means identifying and fixing the guest-side crash, or confirming ownership and whether a fix already exists.
Written by the indexing model from the issue text.
Description
Reproducible guest Vulkan driver crash, independent of GPUI/wgpu
Android Emulator 37.2.12.0 build16428233 on macOS Apple Silicon with Android36.1 google_apis_playstore arm64-v8a image BP41.250822.007/14045093 (kernel6.12.38) crashes on vkSetDebugUtilsObjectNameEXT for a freshly created descriptor-set layout. Emulator36.1.9 exhibits same crash. Command: emulator -avd MyRemotely-GPUI -port5580 -no-snapshot -no-boot-anim -no-audio -no-window -gpu swiftshader. Vulkan/debug utils kept enabled; no workaround suppresses validation.
Original Rust app reaches first wgpu Device indirect-validation bind-group creation, then SIGSEGV in /vendor/lib64/hw/vulkan.ranchu.so vk_common_SetDebugUtilsObjectNameEXT at pc0x10fbf0. Its ash handle naming call uses the correct VkObjectType from the Handle trait immediately after successful create_descriptor_set_layout. A standalone C++ reproducer removes Rust/wgpu/GPUI completely and still exits139 while naming a valid freshly-created descriptor set layout.
Minimal program steps: create VkInstance with VK_EXT_debug_utils, enumerate physical devices, create VkDevice graphics queue, vkCreateDescriptorSetLayout with empty bindings, obtain vkSetDebugUtilsObjectNameEXT using vkGetDeviceProcAddr, VkDebugUtilsObjectNameInfoEXT objectType=VK_OBJECT_TYPE_DESCRIPTOR_SET_LAYOUT and objectHandle=reinterpret_cast<uint64_t>(layout), call. Expected VK_SUCCESS; actual SIGSEGV. Standalone printed handle b400007ba6003030 then exited139.
Can maintainers confirm ownership of the guest-side Mesa naming function and whether this image/backend combination has an existing fix? We can provide full minimal source and tombstone. No client-side disable-debug-naming patch proposed, since that would conceal the valid-call driver error rather than fix it.
- Dominant language
- C++
- Stars
- 60
- Forks
- 41
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from google/gfxstream
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
google/gfxstream#192 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
google/gfxstream#202 · 3 comments ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
google/gfxstream#201 · 7 comments ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
google/gfxstream#198 · 1 comment ·
Maintainers usually reply within 2 days
-
Android Emulator host SIGSEGV in gfxstream GL fence wait path (EmulatedEglFenceSync / tcmalloc)Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
google/gfxstream#191 · 2 comments ·
Maintainers usually reply within 2 days
All issues in google/gfxstream
Similar issues
-
ai_p1 comp-message-queues
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ClickHouse/ClickHouse#125890 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
redis/memtier_benchmark#642 ·
Maintainers usually reply within 1 day
-
Ctrl-C can abort a node: the state timer asks for the node names after shutdownPossibly taken @fmrico claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fmrico/cascade_lifecycle#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100