Opened 14 years ago
Closed 13 years ago
#8838 closed defect (fixed)
Compiling Boost C++ libraries with 8 threads causes VM to reboot
| Reported by: | Ken Yee | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.0.6 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Windows |
Description (last modified by )
VM is 64-bit Debian Squeeze running in 32-bit Vista host. Give the VM 768MB-1.3GB of memory (tried varying it to see if it would help) and run the following command to build the Boost C++ libraries:
bjam --prefix=/usr/local -j 8 --without-mpi --without-python cxxflags=--no-strict-aliasing toolset=gcc variant=release --layout=tagged link=static,shared threading=single,multi -d 2
Doing -j 2 or using the default of 1 thread seems to work fine. The VM should give an out of memory error instead of what it does now. Eventually, the Boost build will lock up so the screen in the VM goes black and your cursor is sometimes visible. Other times, the VM will spontaneously reboot. One time, I saw VirtualBox totally crash.
I think this is happening because compiling w/ multiple gcc threads is very memory and it runs out of memory. Swap is set to 720MB but it doesn't seem to be used much.
Attachments (1)
Change History (7)
by , 14 years ago
| Attachment: | debtest_6x64-2011-05-03-14-09-18.BoostCompileHang.log added |
|---|
comment:1 by , 13 years ago
comment:2 by , 13 years ago
There were several SMP fixes in later VBox 4.0 versions and in VBox 4.1. Is the original problem still relevant with VBox 4.0.12 / 4.1.2?
comment:3 by , 13 years ago
Just confirmed a compile (just a straight make instead of make -j 2) with 4.1.2 (latest VirtualBox) and it still happens. The VM has only one processor allocated to it on a dual-processor host machine.
Alan: is there any way verify that Linux ran out of memory and caused the VM to reboot? I thought Linux would degrade more gracefully (killing off gcc instead of causing the machine to reboot)...
comment:5 by , 13 years ago
So I'm a bit surprised, but it looks like VBox 4.1.4 has fixed this problem.
I watched vmstat and "free -m" on the VM and it looks like it's not running out of memory (what Alan mentioned), but the VM doesn't reboot any more when I do a multithreaded compile... :-)
comment:6 by , 13 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
The Guru Meditation you observed might be fixed in the upcoming 4.1.18 release (out soon).
I have seen similar problems on a Mac OS X host with an Ubuntu guest when compiling complex c++ files in parallel and running out of memory, not sure that its a virtual box problem though, could be linux that is crashing