Custom Query (16363 matches)
Results (1333 - 1335 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3341 | invalid | memory leak | ||
| Description |
I'm running VirtualBox on Windows Vista Home Premium x64 with 8 GB RAM. Starting a virtual machine everything is fine but after a while the virtual machine is consuming more and more of physical memory until full usage - and host begins swapping. Sometimes host itself will not respons anymore... It doesn't depend on used OS inside virtual machine. I also tried some hacks - nothing works, problem still exist. |
|||
| #15091 | obsolete | memory could not be written | ||
| Description |
I have installed latest Virtualbox on a Win7 Enterprise 64 bit, and shortly(1-5 sec) after starting a VM it crashes "The memory could not be written" application error. I have tried different OS selection, and the issue occurs even if there is no OS installed/booted. |
|||
| #8643 | fixed | memory corruption in linux guest => Fixed in SVN | ||
| Description |
When running 64bit linux guests with more than 2g of ram on a windows vista or windows 7 host the memory of the guest is corrupted sometimes. I can check the corruption with the "memtester" tool from Charles Cazabon ( the two guest systems i tested, Gentoo and Ubuntu 10.10, both have packages for this ) and trigger it by switching terminals in gentoo from the framebuffer console ( alt-f2, alt-f1, memory corrupted ) or just let the memtester program run in ubuntu and wait a for some time. Note: memtester has to test almost all available memory. The corruption always happens at an offset of 0x458 from a page start with a 64bit value of 0x100500000 being somewhow written to the memory address. This happens with and without guest additions and on the amd-v and intel vt-x platforms i have access to. I'll attach the Vbox.log of the gentoo guest. |
|||

