Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.54f1
6000.1.13f1
6000.2.0b11
6000.3.0a3
6000.4.0a1
Issue ID
UUM-112931
Regression
No
Player for Meta Quest crashes at "(vk::ScratchBuffer::ReserveImpl(unsigned int, vk::CommandBuffer*, vk::FrameNumbers const&)+212)" when using Realtime Probes with Vulkan
Reproduction steps:
1. Open the attached project “ReproProject“
2. Switch to the Android platform if it is not already set to that
3. Make sure that the Debug Symbols setting is set to “Public (Symbol Table)” (Setting is located in Build Profiles Window)
4. Build the Player
5. Install the built .apk to a Meta Quest device
6. Launch the installed app on the Meta Quest device
7. Accept any permissions that appear.
8. Click 'Play' under 'Art Benchmark'
9. Wait for the Player to finish loading (if the Player loaded into the Scene successfully, the issue did not reproduce)
10. Observe the crash
Expected result: The Player loaded into the next Scene
Actual result: The Player crashes
Reproducible in: 6000.0.54f1, 6000.1.13f1, 6000.2.0b11, 6000.3.0a3
Reproducible on: Windows 11
Not reproducible in: No other environments tested
Reproducible on devices:
- Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno (TM) 740
- Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650
Notes:
- Only reproduces on Vulkan
- The reproduction is highly inconsistent. Repeat steps 5 and 6 until the issue reproduces
- Due to the highly inconsistent reproduction, regression testing will not be conducted
- This issue only reproduces on the first launch of the app. Reinstall the app to reproduce again
- The reproduction produces stack trace different from the originally reported
- When testing in 6000.3.0a3, an error is being logged continuously in the Console window. Does not affect repro steps
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
This issue is timing sensitive and cannot be reproduced under a debugger or when logs are added. We have no way of verifying our potential blind fix and will be closing this as discussed with the reporter.
If this issue comes up again and can be more reliably reproduced, please re-open and we can investigate further.