VBox 5.0.10 Aborts Guest session on resume

[RobCIQ]

May be similar to #13874 but that was resolved... I am running VBox for over a year and never experienced this, until running v5.0.10. All of a sudden now my guest session (Ubuntu 12.04 LTS with kernel 3.2.0-95) aborts when my MacBook Pro awakens (OS Mavericks). This has happened several times and while I cannot reproduce at will, it is quite frequent.

[RobCIQ]

Log file

[Frank Mehnert]

I fear that we need a core dump to debug your problem. But you could also try the most recent test build first.

[RobCIQ]

OK, that was easy... Here's what I did:

robs-macbook:~ rob$ ulimit -c unlimited robs-macbook:~ rob$ /Applications/VirtualBox.app/Contents/MacOS/VirtualBox -startvm "ChartIQ Linux" Segmentation fault: 11 (core dumped) robs-macbook:~ rob$

1. VM started up, I did not log into it yet.
2. Closed the MacBook lid.
3. Reset my router from the button on the back of it
4. Waited around 10 seconds
5. Opened the MacBook lid
6. The VM was visible right where I had left it, the network connection had been reestablished on my Mac
7. Once the VM screen changed from "grayed out" to "active", it just...disappeared.

[RobCIQ]

VBox.log_w-coredump

[RobCIQ]

I tried this process 2 more times but the VM did not abort.

[RobCIQ]

I am attaching a second core dump. The history behind this run was that I my host was connected to a mobile hotspot and disconnected. When I arrived at my office my host connected to a different WiFi network and the guest aborted.

[RobCIQ]

second core dump

[Frank Mehnert]

Sorry, when talking about a core dump, I really mean the core dump and not the VBox.log file. A core dump is a file containing the memory content of the process at the time it crashed. This is described in the link I posted above. The VBox.log file is required as well but we cannot go forward without a core dump.

[Frank Mehnert]

Thank you for the core dump. I've got a backtrace but it's not 100% clear where the problem is. The backtrace might hint to a bug which was recently fixed on Mac OS X. Could you try if you can reproduce the problem with the latest Mac OS X test build from here?

[RobCIQ]

It's been about 2 weeks running on the test build and I have not experienced any issues. So hopefully it has been fixed there.

[Frank Mehnert]

Thanks for letting us know. Please reopen if still relevant.

[RobCIQ]

Related to 13874 for sure, please see comments there. It is happening again in Version 5.1.26 r117224 (Qt5.6.2)

[Frank Mehnert]

Please try the most recent 5.1 test build. The relevant crash should be fixed there. Please confirm.

[RobCIQ]

I think it might be ok. I'll play with the version a little more.

[RobCIQ]

Looks good! Thanks