Crash: VR Scene Inspection on Virtual Desktop + PC with Intel Integrated graphics. #35
Assignees
Triager-bot
Clear assignees
Triager-bot
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Triager-bot/blender-bug-reports#35
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Original bug report: https://projects.blender.org/blender/blender/issues/157206
System Information
Operating system: Windows 11
Graphics card: Intel Arc 140V (Integrated graphics for Intel Ultra 258V processor)
Blender Version
Broken: 5.0.0, 5.1.1 release candidate
Worked: None
Short description of error
Expected: The program should not crash.
Observed: The program crashes.
Exact steps for others to reproduce the error
I tested
hello_xr.exeon the same machine and setup, and it works fine. So, this seems to be a problem inside Blender source code.https://github.com/KhronosGroup/OpenXR-SDK-Source.\bin\.\hello_xr.exe -g Vulkan2or.\bin\.\hello_xr.exe -g VulkanReport is clear
LLM Reasoning
Got it, let's see. The bug report has a clear title, system info (but we ignore that), Blender versions, short description, and exact steps to reproduce. The steps are numbered and specific: connect headset via Virtual Desktop, launch Blender, enable VR plugin, start session, observe crash. Also mentions testing hello_xr.exe which works, so it's pointing to Blender's code. The description is clear about expected vs observed. So the clarity of the text and steps is good. So answer is Yes.
JSON Data
{
"llm_judgement": true,
"processing_time": 6.886326
}
Report is specific
LLM Reasoning
Got it, let's analyze this bug report. The title mentions "Crash: VR Scene Inspection on Virtual Desktop + PC with Intel Integrated graphics." Then the steps are specific: connect VR headset via Virtual Desktop, launch Blender, enable VR plugin, start session, observe crash. Also, they tested another app (hello_xr.exe) which works, so it's a specific issue related to Blender's VR feature on that setup. The report is about a particular scenario (VR Scene Inspection with Intel integrated graphics and Virtual Desktop), not a vague "crashing while rendering" but a specific case. So the answer should be 'Specific'.
JSON Data
{
"llm_judgement": true,
"processing_time": 8.286508
}
Report flagged as NOT a duplicate by LLM
Crash when using Vulkan
https://projects.blender.org/blender/blender/issues/151701
System Information
Operating system: Windows-10-10.0.26100-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 591.44 Opengl Backend
Blender Version
Broken: version: 5.0.0, branch: blender-v5.0-release, commit date: 2025-11-18 09:54, hash:
a37564c4df7aWorked: (newest version of Blender that worked as expected)
Short description of error
The laptop I'm using is an ASUS with a 4060.Help Plz!!!
Exact steps for others to reproduce the error
Use Vulkan baskend, create a new window or open the settings.
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the description and steps.
Bug report 1 is about crashing when using VR Scene Inspection with Intel integrated graphics via Virtual Desktop. The steps involve connecting VR headset, launching Blender, enabling VR plugin, starting VR session, then crash. Also mentions hello_xr.exe works, so it's a Blender issue.
Bug report 2 is about crashing when using Vulkan backend on an NVIDIA GPU. Steps are to use Vulkan backend and create new window or open settings. The system info has different OS (Windows 10 vs 11) and graphics card (NVIDIA vs Intel).
The key here is the cause: one is VR + Intel integrated, the other is Vulkan + NVIDIA. Different setups, different triggers. So they're not the same issue. Therefore, answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 12.145337,
"duplicate_report_number": "151701"
}
Report flagged as NOT a duplicate by LLM
Blender 5.1 crashes
https://projects.blender.org/blender/blender/issues/153578
System Information
Operating system: Windows-10-10.0.26200-SP0 64 Bits
Graphics card: D3D12 (Qualcomm(R) Adreno(TM) X1-85 GPU) Microsoft Corporation 4.6 (Core Profile) Mesa 26.0.0-devel (git-b36be3abdc) Opengl Backend
Blender Version
Broken: version:blender-5.1.0-alpha+main.5549bc572398-windows.arm64-release`
Worked: 5.0
Short description of error
Crashes at start with the message that file VCRUNTIME140D.dll was not found.
Exact steps for others to reproduce the error
Run Blender and it crashes.
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the description and steps to reproduce.
Bug Report 1: The issue is a crash when using VR Scene Inspection on Virtual Desktop with Intel integrated graphics. Steps involve connecting VR headset via Virtual Desktop, launching Blender, enabling VR plugin, starting VR session, then crashing. Also mentions hello_xr.exe works, so it's specific to Blender's code.
Bug Report 2: Crash at start with VCRUNTIME140D.dll not found. Steps are just running Blender and it crashes. The error is about a missing DLL, which is different from the VR-related crash in Report 1.
The descriptions and reproduction steps are completely different. One is VR plugin crash on Intel graphics, the other is startup crash due to missing DLL. So they're not the same issue.
JSON Data
{
"llm_judgement": false,
"processing_time": 11.972149,
"duplicate_report_number": "153578"
}
Report flagged as NOT a duplicate by LLM
Crash when starting a VR Session using SteamVR
https://projects.blender.org/blender/blender/issues/78267
System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14
Operating system: Linux-5.3.0-61-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100
OpenXR Runtime: SteamVR beta Version 1.13.7 (1593046119) Built Jun 25, 2020 at 02:48
HMD: Valve Index
Blender Version
Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-06-25 11:54, hash:
8903368490Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-06-24 21:51, hash:
ec776f18ffWorked: version: 2.90.0 Alpha, branch: master, commit date: 2020-06-23 21:54, hash:
49234c15e2Addon Information
Name: VR Scene Inspection (0, 2, 0)
Author: Julian Eisel (Severin)
Short description of error
Blender crashes when trying to start a VR Session using SteamVR
Exact steps for others to reproduce the error
Notes
I get the crash on Linux and Windows.
In Windows I was able to get a glimpse of the following error message just before the crash:
Crash log for Windows is here:
blender.crash.txt
Crash log for Linux is here:
blender.crash.txt
LLM Reasoning
Got it, let's analyze the two bug reports. First, look at the key sections: description and steps to reproduce.
Bug Report 1:
Bug Report 2:
Now, check if the core issue is the same. The first report is about Intel integrated graphics with Virtual Desktop, the second is NVIDIA RTX with SteamVR (Valve Index). Different hardware setups, different VR runtimes (Virtual Desktop vs SteamVR), and different error messages. The steps are similar in that they involve starting a VR session, but the environments are distinct. So they're not the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 16.374813,
"duplicate_report_number": "78267"
}