VirtualBox crashed with signal 5 in RTSemEventSignal() - it always does if left unattended for a while

[Vital Urbonavi]

Binary package hint: virtualbox-ose

VirtualBox 1.56 OSE on Hardy beta with AMD64 running Windows XP always crashes if left unattended. It never crashed while I was working on/in it. If left unattended (meaning computer left alone) it would crash in about 1 to 2 hours. It seems to function fine if I get back to my computer (including at least taking a look at VB) every half hour or so.

Another, not any less weird and I am not sure even related thing, is that sometimes WinXP in VB starts slow and sometimes fast - no VB settings changed. I thought the pattern was reliably every second time. When it starts fast - it is amazingly fast. I boots and shuts down,(both separately) in about 15 secs - very zippy - pleasure to work with (I wish Gnome was that zippy). When it is slow - it is really slow - unusable. However after shutting it down and starting - it is fast again. Again, all this no VB setting being played with.
It seems to toggle, fast-slow. However I succeeded to have a fast-fast sequence - I think fast-fast happens if I shut down not long after it was started.

Please let me know what more info should I provide. It is a great product and it would be really nice to have it working properly.

Latest log:
Log created: 2008-03-25T08:41:30.385477000Z
Executable: /usr/lib/virtualbox/VirtualBox
Arg[0]: /usr/lib/virtualbox/VirtualBox
Arg[1]: -comment
Arg[2]: WindowsXP
Arg[3]: -startvm
Arg[4]: 9e173d8f-f02c-49e2-2ea6-a304993ac491

!!Assertion Failed!!
Expression: i < 4096
Location : /build/buildd/virtualbox-ose-1.5.6-dfsg/src/VBox/Runtime/r3/linux/sems-linux.cpp(219) int RTSemEventSignal(RTSEMEVENTINTERNAL*)
iCur=0x1 pIntEventSem=00000000009eecf0

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 25 01:41:30 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/virtualbox/VirtualBox
NonfreeKernelModules: nvidia ath_hal
Package: virtualbox-ose 1.5.6-dfsg-2ubuntu2
PackageArchitecture: amd64
ProcCmdline: /usr/lib/usernamertualbox/VirtualBox -comment WindowsXP -startvm 9e173d8f-f02c-49e2-2ea6-a304993ac491
ProcEnviron:
 PATH=/usr/bin:/bin:/usr/sbin:/sbin
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: virtualbox-ose
StacktraceTop:
 RTSemEventSignal ()
 TMVirtualGetEx ()
 TMTimerSetMillies ()
 ?? () from /usr/lib/usernamertualbox/VBoxVMM.so
 VMR3WaitHalted ()
Title: VirtualBox crashed with signal 5 in RTSemEventSignal()
Uname: Linux 2.6.24-12-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy kvm lpadmin netdev plugdev scanner vboxusers video

[Daniel Hahler (blueyed)]

Thank you for your bug report.
I've found the bug already reported upstream on virtualbox.org and linked it.

[Steve Dodd (anarchetic)]

Incidentally, the start up speed variation is probably due to the virtual hard disk contents being cached (or not).

[Felix Geyer (debfx)]

Should be fixed with virtualbox-ose 3.0.6 in karmic.