VirtualBox

Ticket #20483 (awaitsfeedback defect)

Opened 16 months ago

Last modified 15 months ago

Virtubox crashes when the vbox window was resized. Host Windows 10 Pro (64-bit), guest Debian GNU/Linux

Reported by: zephyrus Owned by: gombara
Component: host support Version: VirtualBox 6.1.22
Keywords: Cc:
Guest type: Linux Host type: Windows

Description

Host: Edition Windows 10 Pro (64-bit) version 21H1 Installed ‎2020/‎12/‎16 OS build 19043.1110 Experience Windows Feature Experience Pack 120.2212.3530.0

Guest: Debian GNU/Linux

When I try to resize the VBox window under Windows 10 Pro (64-bit) by grabbing the right edge and tried to shrink the width, VBox crashed.

It seems it encountered exception. Funny, I see screen count changed or something to that effect in the attached log. I only have a single physical display.

TIA

Attachments

VBox.log Download (206.9 KB) - added by zephyrus 16 months ago.
Log file when the crash happened.

Change History

Changed 16 months ago by zephyrus

Log file when the crash happened.

comment:1 Changed 16 months ago by zephyrus

From the log, VBox seemed to think that the guest screen count changed. But no way, I have only a single physical display and my linux install is pretty much straight-forward.

I would rather suspect memory allocation issue. On line 2108, I see pvVRAM=0000000000000000 suggesting that the (newly allocated?) pvBRAM may be possibly assigned a null pointer due to memory stavation?

    ... somewhat old log lines are omitted ...
    ... Obviously, my attempt to resize VBox window resulted in the guest screen resize ... 

2105	45:27:06.945307 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 3188x1992 if necessary
2106	45:27:07.182517 VMMDev: SetVideoModeHint: Got a video mode hint (3188x1992x32)@(0x0),(1;0) at 0
2107	45:27:07.184920 VMMDev: Guest Log: RRScreenChangeNotify event received
2108	45:27:07.186404 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=3840 h=1992 bpp=0 cbLine=0x0 flags=0x2 origin=0,0
2109	45:27:07.190187 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 3188x1992 if necessary
2110	45:27:07.197967 VMMDev: SetVideoModeHint: Got a video mode hint (3188x1992x0)@(0x0),(1;0) at 0
2111	45:27:07.198129 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 3188x1992 if necessary
2112	45:27:07.206966 VMMDev: SetVideoModeHint: Got a video mode hint (3188x1992x0)@(0x0),(1;0) at 0
2113	45:27:07.255552 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2716x1992 if necessary
2114	45:27:07.279434 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000001fb30000 w=3188 h=1992 bpp=32 cbLine=0x31D0 flags=0x1 origin=0,0
2115	45:27:07.296116 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=3188 h=1992 bpp=0 cbLine=0x0 flags=0x2 origin=0,0
2116	45:27:07.323444 VMMDev: SetVideoModeHint: Got a video mode hint (2716x1992x0)@(0x0),(1;0) at 0
2117	45:27:07.364688 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000001fb30000 w=3188 h=1992 bpp=32 cbLine=0x31D0 flags=0x1 origin=0,0
2118	45:27:07.396462 GUI: UIMediumEnumerator: Medium-enumeration finished!
2119	45:27:07.430005 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=3188 h=1992 bpp=0 cbLine=0x0 flags=0x2 origin=0,0
2120	45:27:07.434762 GUI: UIMachineLogic: Guest-screen count changed
2121	45:27:07.438801 GUI: UIMachineLogic: Guest-screen count changed
2122	45:27:07.472909 GUI: UIMediumEnumerator: Medium-enumeration finished!
2123	45:27:07.511142 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000001fb30000 w=2716 h=1992 bpp=32 cbLine=0x2A70 flags=0x1 origin=0,0
2124	45:27:07.603161 GUI: UIMachineLogic: Guest-screen count changed
2125	45:27:07.608522 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2716x1992 if necessary
2126	45:27:07.680078 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2452x1992 if necessary
2127	45:27:07.752204 VMMDev: SetVideoModeHint: Got a video mode hint (2452x1992x32)@(0x0),(1;0) at 0
2128	45:27:07.782350 GUI: UIMediumEnumerator: Medium-enumeration finished!
2129	45:27:07.816336 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2452x1992 if necessary
2130	45:27:07.873645 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2454x1992 if necessary
2131	45:27:07.936422 VMMDev: SetVideoModeHint: Got a video mode hint (2454x1992x32)@(0x0),(1;0) at 0
2132	45:27:07.989307 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2456x1992 if necessary
2133	45:27:08.078173 VMMDev: SetVideoModeHint: Got a video mode hint (2456x1992x32)@(0x0),(1;0) at 0
2134	45:27:08.092864 GUI: UIMediumEnumerator: Medium-enumeration finished!
2135	45:27:08.135736 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2456x1992 if necessary
2136	45:27:08.137219 VMMDev: SetVideoModeHint: Got a video mode hint (2456x1992x32)@(0x0),(1;0) at 0
2137	45:27:08.253063 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2456x1992 if necessary
2138	45:27:08.254922 VMMDev: SetVideoModeHint: Got a video mode hint (2456x1992x32)@(0x0),(1;0) at 0
2139	45:27:08.503805 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=2716 h=1992 bpp=0 cbLine=0x0 flags=0x2 origin=0,0
2140	45:27:08.537000 VMMDev: Guest Log: Monitor 0 (w,h)=(2716,1992) (x,y)=(0,0)
2141	45:27:08.556406 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000001fb30000 w=2452 h=1992 bpp=32 cbLine=0x2650 flags=0x1 origin=0,0
2142	45:27:08.556635 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=2452 h=1992 bpp=0 cbLine=0x0 flags=0x2 origin=0,0
2143	45:27:08.649552 GUI: UIMachineLogic: Guest-screen count changed
2144	45:27:08.655857
2145	45:27:08.655859 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000e57c!!! 

   ... the rest omitted ...

comment:2 Changed 15 months ago by gombara

  • Owner set to gombara
  • Status changed from new to assigned

comment:3 Changed 15 months ago by gombara

  • Status changed from assigned to awaitsfeedback

comment:4 Changed 15 months ago by gombara

Hello.

What is the Debian version and used desktop environment? It is relevant since guest desktop resizing uses different code paths on X11 and wayland desktops.

Last edited 15 months ago by gombara (previous) (diff)

comment:5 Changed 15 months ago by gombara

And do upload the whole log please.

comment:6 Changed 15 months ago by zephyrus

Debian version. Oops, I have updated the version since my report. Let me see. On August 1 when the bug was reported, and actually the crashing Vbox was started on July 30, according to the log line:

Log opened 2021-07-30T06:45:08.410085500Z

(from the log file attached in the original post).

I was using Debian GNU/linux kernel 5.10.0-7-amd64.

env LC_ALL=C ls -lt /boot/vmlinuz*
...
-rw-r--r-- 1 root root 6821216 Aug  3 14:50 /boot/vmlinuz-5.10.0-8-amd64
-rw-r--r-- 1 root root 6818304 May 28 17:31 /boot/vmlinuz-5.10.0-7-amd64 <---
-rw-r--r-- 1 root root 5731056 Nov 28  2020 /boot/vmlinuz-5.9.0-4-amd64
-rw-r--r-- 1 root root 5678672 Sep 19  2020 /boot/vmlinuz-5.8.0-2-amd64
-rw-r--r-- 1 root root 5751952 Apr 29  2020 /boot/vmlinuz-5.6.0-1-amd64

I am using xfce4.

Presumably it is X11 (?) based. Debian Wiki on Wayland states XFCE is unsupported.

 https://wiki.debian.org/Wayland#XFCE_.28unsupported.29

Partial excerpt from "ps axg" output.

   2214 tty7     Ssl+ 424:17 /usr/lib/xorg/Xorg :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
   2215 tty1     Ss+    0:00 /sbin/agetty -o -p -- \u --noclear tty1 linux
   2255 ?        SNsl   0:19 /usr/libexec/rtkit-daemon
   2341 ?        Ssl    0:16 xfce4-session

As for the VBox.log, isn't the VBox.log attached to the original post enough?

https://www.virtualbox.org/attachment/ticket/20483/VBox.log

(I am afraid the logs have been rotated already and no other logs from July 30 are left behind.)

comment:7 Changed 15 months ago by gombara

We are interested (among other things) the GA version installed during said bug was happening. It is always better to post the whole log (it is a few hundreds of kilobytes anyway) than playing the guessing game. Do you still see this crash?

Last edited 15 months ago by gombara (previous) (diff)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use