segfault in VBoxSharedCrOpenGL.so restarting Win10 guest saved under VBox 5.0.6(?)

[Jim Avera]

After installing 5.0.10 from ​http://download.virtualbox.org/virtualbox/5.0.10/virtualbox-5.0_5.0.10-104061~Ubuntu~wily_amd64.deb (Note: 5.0.10 is not an option in the bug ticket drop-down), my previously-saved VMs running Windows 10 crash instantly when started. They were saved (with the VM running) under an earlier version of vbox 5.0 (I think 5.0.6, whatever was in Ubuntu 15.10 as of 11/08/2015).

However I can boot the aborted VM successfully. The problem is only that sessions saved in a previous 5.0 release can not be restarted.

Note: The VM was previously running an app which used Open GL (sketchup), although the app was stopped before saving the VM.

kern.log says:

show_signal_msg: 54 callbacks suppressed VDMA[5886]: segfault at 0 ip 00007f79fd5ca9d5 sp 00007f79c40e6a40 error 4 in VBoxSharedCrOpenGL.so[7f79fd59f000+112000]

I will attach the VBox.log file

[Jim Avera]

The exact same crash (seemingly) happens upon entering Seamless mode after a clean boot of the Win10 guest. Happens every time.

I have NVidia graphics, running Ubuntu 15.10 withy X.Org 1.17.2

kern.log has exactly the same segfault message as reported above.

I'll attach the VBox.log file for this crash as "seamless_crash_Vbox.log" (it shows many assertion failures)

[Jim Avera]

VBox.log from segfault upon entering Seamless Mode

[audvare]

I am getting this when I disconnect from Remote Display, regardless of client. I am attaching the log, although I do not see anything of interest there. My kernel log shows:

May 10 14:09:22 limelight kernel: VDMA[14038]: segfault at 0 ip           (null) sp 00007f9829c83aa8 error 14 in VBoxHeadless[400000+8000]

May 10 14:13:27 limelight kernel: VDMA[16761]: segfault at 14 ip 0000000000000014 sp 00007f819081faa8 error 14 in VirtualBox[400000+8000]