VB Crashes Once A Day After Update To 5.1.2 r108956

[AYSabre]

Since updating to 5.1.2 r108956, I would be working in the VM and boom, VB would just crash with the "Application Error" dialog (see attached image). The manager shows the VM as Aborted. I can then restart it and it seems fine but my concern is my files getting corrupted like my local Outlook files etc. that do not get properly closed when this happens.

My GUEST is a Windows 7 Ultimate 64bit OS. I always install the update immediately followed by installing the extension pack.
My HOST is Windows 7 Enterprise 64bit.

[AYSabre]

Crashed again just now. I attached an image of the VB Manager settings if that may help.

[socratis]

1. Start the VM. Not from a saved or suspended state. Clean start.
2. Take the steps required to generate/observe the error. In your case, just wait?
3. When the VM aborts, right-click on the VM in the VirtualBox Manager. Select "Show Log..."
4. Save it (just the first log), ZIP it and attach it in your response (see the "Upload attachment" at the bottom of the form).

[AYSabre]

1. Start the VM. Not from a saved or suspended state. Clean start.
2. Take the steps required to generate/observe the error. In your case, just wait?
3. When the VM aborts, right-click on the VM in the VirtualBox Manager. Select "Show Log..."
4. Save it (just the first log), ZIP it and attach it in your response (see the "Upload attachment" at the bottom of the form).

I wish I had checked here this morning first. It just happened again this morning but I had restarted it already. I'll grab the log tomorrow after it happens. Thanks.

[AYSabre]

Hi, well it finally happened again. I was wondering if it was going to at this point since it took much longer to happen this time around since last time. I've attached the log file.

Something that may be of note. When the VM came up, it was NOT able to "see" the internet connection and it's configured to use NAT. What I typically do when that happens is either disable the network adapter in Windows and re-enable it or I change the VM configuration to Bridged and save it, then go back in and change it back to NAT. Both of these will reconnect the guest back to the host and properly "see" the internet. It seems that the issue does coincide with when I have to do this as I haven't had to do it for a week and that's about the time frame of the last crash. So it may be network related or I may be way off. Again, this only started happening after I upgraded to the version on this topic.

[AYSabre]

I just saw that there's a new version. I'm going to grab it and update and see what happens going forward.

[danf84]

I reported this here:
https://www.virtualbox.org/ticket/15795

Not had a crash since 5.1.4

[socratis]

Well, then test it a little bit more and report here and, more importantly, in the bug report.

[AYSabre]

Version 5.1.4 r110228 (Qt5.5.1)

I just had the same thing happen today after the upgrade. Did NOT have any network issues that I mentioned previously so probably not related and happened to be a coincidence. I've included the log from immediately after the crash.

My extension pack is also up to date.

[AYSabre]

I reported this here:
https://www.virtualbox.org/ticket/15795

Not had a crash since 5.1.4

Thanks for mentioning this. I added my input there and will try turning off audio for now to see if that stops the crash.

[pentagonik]

I've uploaded a new test build which hopefully should fix the problem:

The files can be downloaded from this page: https://www.virtualbox.org/wiki/Testbuilds

Scroll down to the '''Development Snapshots''' and download the build apppropriate for your host platform.

Could you please try this and provide the usual VBox log files afterwards then?

'This test build is not intended for production use!

Thank you!

[AYSabre]

I've uploaded a new test build which hopefully should fix the problem:

The files can be downloaded from this page: https://www.virtualbox.org/wiki/Testbuilds

Scroll down to the '''Development Snapshots''' and download the build apppropriate for your host platform.

Could you please try this and provide the usual VBox log files afterwards then?

'This test build is not intended for production use!

Thank you!

Thank you for this build. I had not seen this post due to the issue has not come up until today again with the latest release build 5.1.6 r110634. Do you still want me to grab the special build and try it? I'll be posting the latest log in the bug.

[pentagonik]

@AYSabre Testing a development build is not necessary, however, if this still happens for you using 5.1.6 then please provide an audio debug log file as described here:
https://www.virtualbox.org/wiki/AudioDebug

Thank you!

[AYSabre]

@AYSabre Testing a development build is not necessary, however, if this still happens for you using 5.1.6 then please provide an audio debug log file as described here:
https://www.virtualbox.org/wiki/AudioDebug

Thank you!

Will this work since I have audio disabled in my VM settings?

[pentagonik]

@AYSabre Testing a development build is not necessary, however, if this still happens for you using 5.1.6 then please provide an audio debug log file as described here:
https://www.virtualbox.org/wiki/AudioDebug

Thank you!

Will this work since I have audio disabled in my VM settings?

Oh, VBox crashes even with disabled audio? Then the audio debug file of course is not needed. Please search for a similar bug ticket or open a new one and attach a core (dump) to this defect.