VM settings not always saved when VMM closed

Description

I noticed this when changing a VM (that I had just taken a snapshot of) to have more memory for "next time", ie, I made the change but exited the VMM without restarting the VM. When I next started the VMM, the VM memory change had been lost. It seems the .vbox file was not written.

To reproduce:

start VMM

select a VM that is identical to its last snapshot [I think this is required]

change memory setting of the VM [verify VMM reflects change for VM]

close VMM

start VMM

and I see in the VMM that the change to VM has been lost.

If I start the VM before closing the VMM, then the change is not lost.

Cannot reproduce. Are you really using VBox 4.0.8? And does the VM have snapshots? If so, are all of them online snapshots or offline snapshots?

Yes, I'm using 4.0.8r71778, installed yesterday.

Yes, the VMs have snapshots and all are off-line. As I stated above, I think to see this bug the VM must be identical to its last snapshot.

I reproduced the problem repeatedly with 2 VMs as I was writing the op, one with 2 snapshots, one with 3 snapshots.

I've been trying to reproduce again and it's getting thoroughly bizarre. I changed a VM from 1.5G to 2G. When I restarted the VMM the VM did indeed have 2G. However, I restarted the VMM again and the VM is back to 1.5G. Gah! Playing around, sometimes it takes a single restart of the VMM, sometimes more than one. I'm a bit baffled. VB is installed on a different drive from the VM data, though on the same disk. I'll see if rebooting the host (Win7-64b) makes any difference...