4.2.12 Exiting Full Screen caused Win Server 2012 to abort

[Quickbooks Office]

Exiting Full Screen caused Win Server 2012 to abort

Using VirtualBox 4.2.12 and 4.2.12 guest additions

[Michael Thayer]

You might want to try the latest 4.2 build, as I did fix a crash on mode switches there (not saying it will help, just that it might). I can't offer you a Fedora 18 build, but you can choose between a generic installer script and an OEL/RHEL 6 binary - be sure to uninstall your current package first. Is this reproducible by the way?

​http://www.virtualbox.org/download/testcase/VirtualBox-4.2.13-85354-Linux_amd64.run ​http://www.virtualbox.org/download/testcase/VirtualBox-4.2-4.2.13_85354_el6-1.x86_64.rpm

[Quickbooks Office]

Replying to michael:

You might want to try the latest 4.2 build, as I did fix a crash on mode switches there (not saying it will help, just that it might). I can't offer you a Fedora 18 build, but you can choose between a generic installer script and an OEL/RHEL 6 binary - be sure to uninstall your current package first. Is this reproducible by the way?

​http://www.virtualbox.org/download/testcase/VirtualBox-4.2.13-85354-Linux_amd64.run ​http://www.virtualbox.org/download/testcase/VirtualBox-4.2-4.2.13_85354_el6-1.x86_64.rpm

Can you also provide me with the extpack and guest additions iso file for 4.2.13-85354? Thanks.

[Michael Thayer]

The 4.2.12 ones should be fine. (Or did I miss something?)

[Quickbooks Office]

Now when I exit full screen it becomes black screen.

I am attaching the log file.

[Michael Thayer]

I assume you mean a black guest screen?

[Quickbooks Office]

Replying to michael:

I assume you mean a black guest screen?

Yes. The guest becomes black screen.

[Quickbooks Office]

PASV
227 Entering Passive Mode (141,146,1,166,223,61)
STOR /appsdev/incoming/4.2.13.coredump.Ticket11760.tar.xz
150 Ok to send data.
226 Transfer complete.
Successfully transferred /home/user/4.2.13.coredump.Ticket11760.tar.xz at 59.61 KB/s
SITE CHMOD 664 /appsdev/incoming/4.2.13.coredump.Ticket11760.tar.xz
550 Permission denied.

I uploaded the core dump & log file ==> 4.2.13.coredump.Ticket11760.tar.xz. Please let me know if you get the files.

File(s) may contain sensitive information.

[Quickbooks Office]

Also happens in VirtualBox VM 4.2.51 r85607 ;

Test Build was found here https://www.virtualbox.org/ticket/9659#comment:32 (may 8, 2013)

See: WinServer2012-2013-05-20-12-25-36.log

[Quickbooks Office]

Host ==> VBoxCrWinCmd: segfault / error 4 in libGL.so.1.2.0

May 20 12:04:11 localhost kernel: [  532.622265] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
May 20 12:04:18 localhost dbus-daemon[690]: dbus[690]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
May 20 12:04:18 localhost dbus[690]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
May 20 12:04:18 localhost dbus-daemon[690]: dbus[690]: [system] Successfully activated service 'net.reactivated.Fprint'
May 20 12:04:18 localhost dbus[690]: [system] Successfully activated service 'net.reactivated.Fprint'
May 20 12:04:18 localhost dbus-daemon[690]: Launching FprintObject
May 20 12:04:18 localhost dbus-daemon[690]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
May 20 12:04:18 localhost dbus-daemon[690]: ** Message: entering main loop
May 20 12:04:49 localhost dbus-daemon[690]: ** Message: No devices in use, exit
May 20 12:04:50 localhost dbus-daemon[690]: dbus[690]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
May 20 12:04:50 localhost dbus[690]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
May 20 12:04:50 localhost dbus-daemon[690]: dbus[690]: [system] Successfully activated service 'net.reactivated.Fprint'
May 20 12:04:50 localhost dbus[690]: [system] Successfully activated service 'net.reactivated.Fprint'
May 20 12:04:50 localhost dbus-daemon[690]: Launching FprintObject
May 20 12:04:50 localhost dbus-daemon[690]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
May 20 12:04:50 localhost dbus-daemon[690]: ** Message: entering main loop
May 20 12:05:21 localhost dbus-daemon[690]: ** Message: No devices in use, exit
May 20 12:07:08 localhost kernel: [  709.433156] device p4p1 entered promiscuous mode
May 20 12:09:59 localhost kernel: [  880.203194] device p4p1 left promiscuous mode
May 20 12:09:59 localhost kernel: [  880.293324] device p4p1 entered promiscuous mode
May 20 12:10:01 localhost kernel: [  882.521675] VBoxCrWinCmd[6995]: segfault at 6c8 ip 000000353ea4ac8e sp 00007eff4494bc20 error 4 in libGL.so.1.2.0[353ea00000+7a000]
May 20 12:10:01 localhost kernel: [  882.657147] device p4p1 left promiscuous mode
May 20 12:10:01 localhost kernel: [  882.664344] vboxnetflt: 0 out of 666 packets were not sent (directed to host)
May 20 12:10:18 localhost systemd[1]: Starting Cleanup of Temporary Directories...
May 20 12:10:18 localhost systemd-tmpfiles[7076]: stat(/run/user/1000/gvfs) failed: Permission denied
May 20 12:10:18 localhost systemd[1]: Started Cleanup of Temporary Directories.
May 20 12:11:03 localhost kernel: [  944.633302] device p4p1 entered promiscuous mode
May 20 12:13:55 localhost kernel: [ 1115.636394] VBoxCrWinCmd[7151]: segfault at 6c8 ip 000000353ea4ac8e sp 00007fe72c0b4c20 error 4 in libGL.so.1.2.0[353ea00000+7a000]
May 20 12:13:55 localhost kernel: [ 1115.717952] device p4p1 left promiscuous mode
May 20 12:13:55 localhost kernel: [ 1115.723543] vboxnetflt: 0 out of 536 packets were not sent (directed to host)
May 20 12:14:17 localhost kernel: [ 1138.056853] device p4p1 entered promiscuous mode
May 20 12:21:07 localhost kernel: [ 1547.426792] device p4p1 left promiscuous mode
May 20 12:21:07 localhost kernel: [ 1547.441944] device p4p1 entered promiscuous mode
May 20 12:21:46 localhost kernel: [ 1586.901405] device p4p1 left promiscuous mode
May 20 12:21:48 localhost kernel: [ 1588.289398] vboxnetflt: 0 out of 949 packets were not sent (directed to host)
May 20 12:22:00 localhost kernel: [ 1600.911630] device p4p1 entered promiscuous mode
May 20 12:25:36 localhost kernel: [ 1816.442964] VBoxCrWinCmd[7420]: segfault at 6c8 ip 000000353ea4ac8e sp 00007f1cf1642c20 error 4 in libGL.so.1.2.0[353ea00000+7a000]
May 20 12:25:36 localhost kernel: [ 1816.529000] device p4p1 left promiscuous mode
May 20 12:25:36 localhost kernel: [ 1816.537538] vboxnetflt: 0 out of 522 packets were not sent (directed to host)
May 20 12:59:56 localhost dbus-daemon[690]: dbus[690]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)

[Quickbooks Office]

Using VirtualBox-4.2.51-86055 (May 28 build)

Jun  2 00:22:26 localhost kernel: [ 2475.828547] ShCrOpenGL[2984]: segfault at 4 ip 00007f4da76e39af sp 00007f4dcc630478 error 4 in i965_dri.so[7f4da76c3000+cc000]

Attaching log.

[Quickbooks Office]

Uploaded Core Dump. File Name: coredump.ticket11760.tar.xz

227 Entering Passive Mode (141,146,1,166,204,232)
STOR /appsdev/incoming/coredump.ticket11760.tar.xz
150 Ok to send data.
226 Transfer complete.
Successfully transferred /home/user9/coredump.ticket11760.tar.xz at 105.29 KB/s
SITE CHMOD 664 /appsdev/incoming/coredump.ticket11760.tar.xz
550 Permission denied.

File(s) may contain sensitive information.

[Quickbooks Office]

The crash is harder to reproduce after I updated the Guest Additions to 4.2.51-86055 (May 28 build).

But it still happens occasionally with 3D enabled.

[Quickbooks Office]

Jun 6 16:55:48 localhost kernel: [131824.045501] ShCrOpenGL[4370]: segfault at 4 ip 00007fa209dd29af sp 00007fa20ad15478 error 4 in i965_dri.so[7fa209db2000+cc000]

Jun 6 16:55:48 localhost kernel: [131824.124081] device p4p1 left promiscuous mode

Jun 6 16:55:48 localhost kernel: [131824.135513] vboxnetflt: 0 out of 2229745 packets were not sent (directed to host)

For log file https://www.virtualbox.org/attachment/ticket/11760/WinServer2012-2013-06-06-16-48-37.log

VirtualBox and Guest Additions: 4.2.51-86055 (May 28 build)

[Frank Mehnert]

Please reopen if still relevant with VBox 4.3.10. There is actually a big chance that your crash was fixed in the context of the VBox 4.3.4 release.