[Bug]: VirtualBoxVM segfault in DarwinHidDevicesApplyAndReleaseLedsState after host USB KVM switch (macOS, 7.2.22)

Aperta
  • Qualcosa non va?
#965 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 6 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c, macos
Ambito
desktop, operating-systems

Direzione di ricerca

Start by tracing the macOS host HID handling around DarwinHidDevicesApplyAndReleaseLedsState, named in the crash stack, and inspect how it handles devices after a USB KVM switch. The report includes uploaded logs and a reproduction sequence: switch away and back, then change window focus. Done means reproducing and fixing the null-address crash on the window focus path.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
Version

7.2.22

Host OS Type

macOS

Host OS name + version

Mac Tahoe Version 26.6.2 (25G83)

Host Architecture

ARM

Guest OS Type

macOS

Guest Architecture

ARM

Guest OS name + version

Ubuntu 26.10

Component

Unspecified

What happened?

I have a KVM switch (AV Access iDock C20) to switch between two Mac Book Pro M4 laptops. I'm running VirtualBox only on Mac #1. I switch back-and-forth between the Macs during the day. When I do that, VirtualBox crashes.

Primary error:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 11, Segmentation fault: 11

Environment:

  • VirtualBox 7.2.22 r175245, darwin.arm64 release, running in driverless mode
  • Host: Mac16,5 (M4 Max, 16 cores, 128 GB), macOS 26.6.2 (25G83)
  • Guest: Ubuntu 26.10 (arm64), 16 vCPUs, Guest Additions 6.0.0 reported by guest
How can we reproduce this?

Steps:

  1. Run a VM with the GUI. Keyboard and mouse are connected through a USB KVM
    switch shared with another Mac.
  2. Switch the KVM to the other Mac, then switch back.
  3. Click between the VirtualBox window and other apps.

Result: VirtualBoxVM crashes with EXC_BAD_ACCESS (SIGSEGV), KERN_INVALID_ADDRESS
at 0x0 on the main thread. Crashing stack:
0 IOKit IOHIDDeviceCopyMatchingElements + 44
1 UICommon.dylib
2 UICommon.dylib DarwinHidDevicesApplyAndReleaseLedsState + 512
3 VirtualBoxVM
4 QtCore ... QApplicationPrivate::notify_helper / setActiveWindow
...
QCocoaWindow::windowDidBecomeKey (crash 1) and windowDidResignKey (crash 2)

Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
Lingua principale
C
Stelle
1.4k
Fork
219
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di VirtualBox/virtualbox

Tutte le issue di VirtualBox/virtualbox

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.