Opened 3 years ago
Last modified 3 years ago
#20282 new defect
virtualbox manager (win) crashes when starting on 2nd screen
| Reported by: | gggeek | Owned by: | |
|---|---|---|---|
| Component: | GUI | Version: | VirtualBox 6.1.18 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | other |
Description
The VB Manager app works fine in my current setup (dell latitude 7290 latitude with attached 2nd monitor asus zenscreen via usb-c) if it is started on the main windows screen. It crashes a few seconds after starting if it is started instead on teh 2nd screen. In order to reproduce: start the Manager, vmove it to the 2nd screen, then shut it down, so that it will start there. 2nd screen is set at 125% scaling in windows settings.
Windows event manager says Exception code 0xc0000005, fault offset 0xc)...01f0c38 in Qt5GuiVbox.dll
Attachments (2)
Change History (5)
by , 3 years ago
| Attachment: | vboxerror.png added |
|---|
comment:1 by , 3 years ago
comment:2 by , 3 years ago
Not sure if it related, but ticket #19204 also mention crashes when using 2nd monitor - on linux this time
comment:3 by , 3 years ago
Also, might not relate at all, but it seems that the VB Manager GUI does not 'sense' well the fact that it is moved to a display with 125% scaling factor. Eg: the dialog message that pops up at the end of a 'check for updates' process, stating "You are already running the most recent version of virtualbox": it is ok if the app is on the main monitor, but it uses a wrong font size if it is on the 2nd screen.
by , 3 years ago
| Attachment: | dialog_font_size.png added |
|---|
Host os: win 10 64bit 20H2