Version
7.2.8
Host OS Type
Windows
Host OS name + version
Windows 11 Build 26200
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Guest OS name + version
Soplos Linux Tyron RC1 (Debian Testing, kernel 7.0.9)
Component
3D Support
What happened?
When opening the Kitty terminal emulator inside a Linux guest with VMSVGA graphics controller and 3D Acceleration enabled, VirtualBoxVM.exe crashes immediately with an application error:
"The instruction at 0x00007FF841282D80 referenced memory at 0x0000000000000008. The memory could not be read."
The VM becomes completely unresponsive and must be deleted and recreated. The crash is 100% reproducible every time Kitty is launched. The issue occurs regardless of host hardware (tested on AMD Ryzen 7 8845HS, AMD Ryzen 7 6800H, Intel N150, Intel Core i7).
The crash appears in VBox.log as:
!!! rtR3WinUnhandledXcptFilter caught an exception
ExceptionCode=0xc0000005
ExceptionAddress=00007ff841282d80
ExceptionInformation[1]=0000000000000008
Guest reports OpenGL 4.1 via Mesa 26.0.6 / vmwgfx 2.21.0.0 before the crash.
How can we reproduce this?
- Create a Linux VM with VMSVGA, 256MB video memory, 3D Acceleration enabled
- Install a Debian Testing based Linux distribution with kernel 7.0.x and Mesa 26.x
- Install VirtualBox Guest Additions 7.2.8
- Boot the VM and open Kitty terminal
- VirtualBoxVM.exe crashes immediately
Note: without 3D Acceleration, Kitty opens and works normally. The crash only occurs when 3D Acceleration is enabled and Kitty attempts to initialize an OpenGL context.
VBox.log.1.txt
Did you upload all of your necessary log files, screenshots, etc.?
Version
7.2.8
Host OS Type
Windows
Host OS name + version
Windows 11 Build 26200
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Guest OS name + version
Soplos Linux Tyron RC1 (Debian Testing, kernel 7.0.9)
Component
3D Support
What happened?
When opening the Kitty terminal emulator inside a Linux guest with VMSVGA graphics controller and 3D Acceleration enabled, VirtualBoxVM.exe crashes immediately with an application error:
"The instruction at 0x00007FF841282D80 referenced memory at 0x0000000000000008. The memory could not be read."
The VM becomes completely unresponsive and must be deleted and recreated. The crash is 100% reproducible every time Kitty is launched. The issue occurs regardless of host hardware (tested on AMD Ryzen 7 8845HS, AMD Ryzen 7 6800H, Intel N150, Intel Core i7).
The crash appears in VBox.log as:
!!! rtR3WinUnhandledXcptFilter caught an exception
ExceptionCode=0xc0000005
ExceptionAddress=00007ff841282d80
ExceptionInformation[1]=0000000000000008
Guest reports OpenGL 4.1 via Mesa 26.0.6 / vmwgfx 2.21.0.0 before the crash.
How can we reproduce this?
Note: without 3D Acceleration, Kitty opens and works normally. The crash only occurs when 3D Acceleration is enabled and Kitty attempts to initialize an OpenGL context.
VBox.log.1.txt
Did you upload all of your necessary log files, screenshots, etc.?