Out of memory (Windows 7 64-bit host, Windows 7 64-bit guest)

[David Miller]

Host: Win 7 64-bit, 8GB ram

Guest: Win 7 64-bit, 2GB ram

I left the guest running unattended for a while. When I got back, the Windows out-of-memory routine was running, and I had to shut down the guest.

In the log file, it starts with this message: 00:18:43.194 AioMgr0-N: Request 0x000000926186b0 failed with rc=VERR_UNRESOLVED_ERROR, migrating endpoint T:\VirtualBox VMs\Armedia Work\Armedia Work.vdi to failsafe manager.

Then I see hundreds of these: 02:44:29.244 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display} aText={Could not take a screenshot (VERR_TRY_AGAIN)}, preserve=false

Then hundreds more of these: 03:00:26.416 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display} aText={Could not take a screenshot (VERR_NO_MEMORY)}, preserve=false

Log file is attached.

[David Miller]

ZIP file with vbox.log from the out of memory error

[David Miller]

If it matters, I had a VMware Player VM running at the same time, also using 2GB of memory. The VMware VM was unaffected by the out of memory condition and the Windows host did not close the VMware player.

[Vasiliev]

I have this bug on WinXP SP3 host and xubuntu 9.04 guest. After virtualbox upgrading from 3.0.2 to 4.0.0 i get error "Could not take a screenshot" in log and windows' "out of memory" error then. As i could notice, this error appears, when guest changes it's resolution.

Log is also attached.

[aeichner]

@david The VERR_UNRESOLVED_ERROR is unrelated to the out of memory error but it would be still interesting what error Windows returns there.

The following link contains additional code to log the native error code, can you please install it and upload the VBox.log if the VERR_UNRESOLVED_ERROR appears again? ​http://www.virtualbox.org/download/testcase/VirtualBox-2011-01-05-17-04-28-win-rel-4.0.1-r69273-MultiArch.exe

The out of memory error should be fixed with this build, btw.

[Vasiliev]

Replying to aeichner:

@david

The out of memory error should be fixed with this build, btw.

The problem still happens, but the error code has changed: VERR_TRY_AGAIN. However, first time i started vm it crashed with no error in log.

New logs are attached.

[Vasiliev]

Replying to Vasiliev:

Replying to aeichner:

@david

The out of memory error should be fixed with this build, btw.

The problem still happens, but the error code has changed: VERR_TRY_AGAIN. However, first time i started vm it crashed with no error in log.

New logs are attached.

Also I've noticed, that vm crashes when starting X (i've tested it with starting X from console). Also, i have a thin horizontal stripe of non-black pixels in the vm window with height about 5 pixels.

[Frank Mehnert]

Is that problem still reproducible with VBox 4.1.2?

[Frank Mehnert]

No response, closing.