Shutdown with saving state fails at 98%

[mcontenti]

Same problem happens since update to Vbox 5.2.32 r132073. from 5.2.30.
Host: Ubuntu 16.04.6 LTS, kernel: 4.15.0-55-generic
Guest: Windows 10 build 10586
Log attached (too big, zipped).
Problem seems to disappear disabling 3D acceleration.
This is a regression from 5.2.30 and earlier.

[banzeo]

Ok my issue look like the one described here (post is now locked)
viewtopic.php?f=7&t=93951

I don't have Intel Graphics, but AMD APU with Integrated Vega Graphics (Athlon 200GE with vega graphics)
Disabling 3D acceleration actually fixes my issue, but this is a regression in 5.2.32

Did anyone file a bug report yet ?

[socratis]

I merged several threads, one from the "Linux Hosts" area (Shutdown with saving state fails at 98%) and two from the "Windows Hosts" area (Ubuntu VM crashing when saving state (only with 3d acceleration enabled) and VirtualBox 6.0.10 crash when saving a VM) and moving them to "Using VirtualBox", because they seem to have common crashes, but various hosts and guests.

We just need to find the common denominator...

[socratis]

Did anyone file a bug report yet ?

banzeo, I merged your posts with the existing thread. I've been merging them all day

I haven't searched the bugtracker for 10 days, I'll try to do it later today or tomorrow. As I said previously if we could scratch our heads together to find the common denominator in this, it really helps the developers as well...

[Niffo]

Exactly the same thing here on host Debian 10 (with up to date NVidia Drivers) and Windows Guest.
Disabling 2D/3D Acceleration workarounded the issue.

[socratis]

According to ticket #18802 (cannot do "savestate" machine) this is fixed in SVN/next maintenance.

@ALL
Can you try the latest test builds and report back?

@Niffo
Without a complete, ZIPPED VBox.log, we can only speculate...

[banzeo]

It seems fixed for me in 5.2.33 r133021

[socratis]

Thank you @banzeo for the feedback!