Opened 4 years ago
Last modified 4 years ago
#19599 new defect
[VM Crash] Cannot access memory at 0x00000...
| Reported by: | Chris Doherty | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.1.8 |
| Keywords: | crash | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
My Ubuntu VM will randomly decide to access an inaccessible memory address causing a panic and crash.
I haven't been able to nail this down to a specific event, it seems to happen randomly. If I can identify a reproducible event I'll update the report.
Attachments (3)
Change History (6)
by , 4 years ago
| Attachment: | 2020-05-18-15-55-35-bugreport.tgz added |
|---|
by , 4 years ago
comment:1 by , 4 years ago
After launching my VM, I launch Visual Studio Code. If I rapidly click the menu's I note they come up black. Continuing to rapidly click the menus eventually - 5-10 seconds - triggers the error observed in the attached image.
by , 4 years ago
| Attachment: | IMG_20200518_105409.jpg added |
|---|
comment:2 by , 4 years ago
Attached the segfault I caught from dmesg in the guest OS (no surprises).
comment:3 by , 4 years ago
Reduced the number of CPUs the VM consumes from 10 to 6 (The host has 12 logical cores so 6 is in-line with what the UI seems to think is a valid configuration).
Taking the approach of launching VSCode and clicking through menus indicates the problem has disappeared. Slightly odd.
crash message