Opened 10 years ago
Closed 10 years ago
#14419 closed defect (fixed)
Switching to full screen with mini toolbar enabled crashes guest
Reported by: | Hans Vledder | Owned by: | |
---|---|---|---|
Component: | GUI | Version: | VirtualBox 5.0.0 |
Keywords: | full screen, crash | Cc: | |
Guest type: | Windows | Host type: | Windows |
Description
When switching to full screen on a guest that has its mini toolbar enabled crashed the guest. This problem was introduced in 4.3.16 and is present up to 5.0.0.
Attachments (2)
Change History (8)
by , 10 years ago
Attachment: | Screenshot #1.png added |
---|
follow-ups: 2 3 comment:1 by , 10 years ago
Any change with VBox 5.0.2? If not we would be very interested in a Windows application dump, see here (scroll down this page).
comment:2 by , 10 years ago
comment:3 by , 10 years ago
Replying to frank:
Any change with VBox 5.0.2? If not we would be very interested in a Windows application dump, see here (scroll down this page).
Installed v5.0.2 and ran two test scenarios. The problem introduced in v4.3.16 is still there and its behavior remains unchanged since; full screen mode with the mini toolbar enabled crashes the guest VM on my machine. Please see the attached ZIP file with my test findings. Gut feeling tells me my ATI Radeon HD5450 graphics adapter became an issue as of v4.3.16.
--Hans
Edit: Enabling Windows Application Dump did nothing. The Guest OS doesn't notice the plug is pulled on VirtualBox Guest process.
comment:4 by , 10 years ago
Read here, it might be of help.
To save a memory dump of the crashed VirtualBox process, first you have to trigger the crash, but do not close the crash dialog. Then you need to launch Process Explorer as Administrator, on the host. Look for the lowest VirtualBox process in the VirtualBox process tree (usually it's the one with the larger memory footprint), right click it and click Create Dump - Create Minidump. Compress it and attach it here.
comment:5 by , 10 years ago
Gents,
Running sfc /scannow and rebooting the host system afterwards fixed this long running issue. No dump file analysis needed. Due to this problem I was still running v4.3.12. Thanks very much for your effort! This ticket can be closed now.
--Hans
comment:6 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Screenshort of error message