VM started crashing after update to 4.3.28

[Gog]

One of my Windows VMs started crashing after upgrading to 4.3.28 this weekend. The message is copied below.

I have 4 other VMs, also running Windows 8.1 Pro, headless, with the same configuration, without any problem. It's always the same VM that crashes.

The error is

# *** glibc detected *** /usr/lib/virtualbox/VBoxHeadless: double free or corruption (fasttop): 0x00000000008b4170 ***

======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x75be6)[0x7f4686ea5be6]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7f4686eaa98c]
/usr/lib/virtualbox/VBoxDD.so(+0x1121e7)[0x7f46765a21e7]
/usr/lib/virtualbox/VBoxDD.so(+0x10f3f0)[0x7f467659f3f0]
/usr/lib/virtualbox/VBoxDD.so(+0x107ba3)[0x7f4676597ba3]
/usr/lib/virtualbox/components/VBoxVMM.so(+0xa32b2)[0x7f46801b32b2]
/usr/lib/virtualbox/VBoxRT.so(+0xfc3fc)[0x7f4686aec3fc]
/usr/lib/virtualbox/VBoxRT.so(+0x171c0c)[0x7f4686b61c0c]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7f46873ceb50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f4686f0b95d]

======= Memory map: ========
00400000-00407000 r-xp 00000000 09:02 
262466                             /usr/lib/virtualbox/VBoxHeadless
00607000-00608000 rw-p 00007000 09:02 262466                             /usr/lib/virtualbox/VBoxHeadless
00608000-0060a000 rw-p 00000000 00:00 0
007c1000-009e7000 rw-p 00000000 00:00 0                                  [heap]
7f45ef616000-7f45ef9f6000 rw-p 00000000 00:00 0
7f45efa16000-7f45efc16000 rw-s 00000000 00:04 16648                      /dev/zero (deleted)
7f45efc16000-7f45efe16000 rw-s 00000000 00:04 18682                      /dev/zero (deleted)
7f45efe16000-7f45f0016000 rw-s 00000000 00:04 16647                      /dev/zero (deleted)
7f45f0016000-7f45f0036000 rw-p 00000000 00:00 0
7f45f0056000-7f45f0076000 rw-p 00000000 00:00 0
(...)

[Frank Mehnert]

Please attach the VBox.log file of this VM session. Which was the previous version of VirtualBox which didn't show this problem? Do you have a core dump available?

[Gog]

1. I don't have the VBox.log for this specific session, but I'm attaching the log from a subsequent session that was terminated normally. The VM has been rebuilt.
2. 4.3.12
3. Unfortunately no. The only documentation is what I have attached in the incident report. I truncated it, but the rest is a list of blocks terminated with "/dev/zero (delete)".

[APLU]

Hi,

I got the same issue with Windows 7 as guest and Ubuntu 14.04 as host. Using VirtualBox 4.3.28.

The issue happen only when the host is not connected to the network (wireless or not). It takes about 5/10 minutes for me to get VBox crashing.

I'm attaching a coredump.

[APLU]

The CoreDump is to big to be attached, so I've uploaded here (link will work until 2015-09-30): ​https://www.aplu.fr/clown/index.php/s/fVMbzcHXxgodabl (SHA-1 of uncompressed file: 3dce0b7d91919d703db31a6e75b36e495405d3c8).

As far as I remember, the bug wasn't present with a previous version of VirtualBox.

On my configuration, this bug is reproducible at 100%, I just have to wait a few minutes without doing anything on the host or VM, with the host disconnected.

Regards,