Ticket #2548 (closed defect: fixed)

Opened 10 years ago

Last modified 8 years ago

Saved state is discarded after VERR_NO_MEMORY

Reported by: CaptainFlint Owned by:
Priority: critical Component: other
Version: VirtualBox 2.0.4 Keywords:
Cc: Guest type: other
Host type: Windows


Host OS: WinXP SP3 Guest OS: any

I tried to load a VM which was in saved state, but there was not enough memory on my host machine (many programs loaded), so I got VERR_NO_MEMORY. After that the saved state of this VM silently disappeared: in VB Manager it was shown in "Powered Off" state, and when I tried to open it again, it started loading from scratch, as if I discarded the saved state (which of course I did not). Log file of this VM is attached.


VBox.log Download (36.4 KB) - added by CaptainFlint 10 years ago.
Log file of the VM
debian-2008-11-27-17-20-59.log Download (43.1 KB) - added by kazus_k 9 years ago.
before raising memory
debian-2008-11-27-17-23-09.log Download (43.0 KB) - added by kazus_k 9 years ago.
after.. system discard all changes

Change History

Changed 10 years ago by CaptainFlint

Log file of the VM

comment:1 Changed 9 years ago by kazus_k

i have the same here. i've raised memory used by my VM and it discard all my data and changes.

Changed 9 years ago by kazus_k

before raising memory

Changed 9 years ago by kazus_k

after.. system discard all changes

comment:2 Changed 9 years ago by mbvlist

I'm from #2611 I've got 1GB of host memory in Windows, I think 384MB of RAM in my Guest OS.

I really don't get why Windows would give you an error: at that moment my swapfile was barely used, so it should've just swapped bits of Eclipse/Firefox/Outlook/whatever away. Another indication might be that I closed outlook (200MB), started my virtual machine, and started outlook (again 200MB after loading), and then everything works fine. Maybe you use a different API to register memory, one that's guaranteed to be semi-realtime (which wouldn't give Windows the time to swap applications away). I can imagine that that's a good thing while running the virtual machine, but not while loading the virtual machine.

However, the real problem here is not that the out-of-memory-error appears, it is that the state of the machine is discarded. Can't you just ask if the user would like to try again later, after freeing memory? If it happens while the virtual machine isn't running, that's almost what happens: the machine is paused, and after closing Outlook/Eclipse/Firefox I can start it up again.

comment:3 Changed 9 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to fixed

Fixed in 2.1. An out of memory error could always occur, but your saved state will be kept around.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use