Opened 16 years ago
Last modified 16 years ago
#1129 closed defect
Several VBoxDSL segfaults, during WindowsXP guest shutdowns, opensuse 10.3 32bit host — at Initial Version
| Reported by: | Christopher | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 1.5.4 |
| Keywords: | sefaults segmentation faults shutdown windowsxp opensuse103 | Cc: | |
| Guest type: | other | Host type: | other |
Description
Hello, first of all, thanks for your great work.
Problem: VBoxDSL segfaults in about 1 out of 20 runs. Details: Most of the time, the segfaults occure during WindowsXP shutdowns,
but very rarely also while working with some program, e.g. web-surfing (latter might be something completely different). I found no reproducible conditions. Sessions started (most of the time) from same image; changes were written to a new snapshot file.
Other versions: The same (or similar) problem (with segfaults during shutdown)
was found with VBoxDSL 1.5.2. The "normal" VirtualBox did not show this effect (which might be just a matter of statistics).
Guest: WindowsXP including all patches and much add software (~10GB),
guest-additions 1.5.4 installed, shared folders added (but not used)
Host: OpenSUSE 10.3 32 bit including all patches USB-Mount in /etc/fstab (2305=vboxusers) (if it's important at all):
usbfs on /proc/bus/usb type usbfs (rw,devgid=2305,devmode=640)
SGID-vboxusers: VBoxDSL is started with SGID-vboxusers wrapper,
which hopefully should not be the problem.
Hardware: Athlon 64 X2 or Pentium 4 (segfaults on both hardware architectures)
(tested on several different computers, so it seems NOT to be a hardware defect)
Binary: virtualbox.org/download/1.5.4/VirtualBox-1.5.4_27034_openSUSE103-1.i586.rpm Core: Size of core-dump 1.3 GB. After bzip2 ~70MB.
Dont' know, if I should post such large core files on this list. Can you give me instructions, were to put the core files (I have two different ones at the moment - both segfaults at shutdown)
Can you please help? Many Thanks.
VBox.log:
Intrestingly, all VBoxDSL runs *WITHOUT* segfaults show an "ERROR" tag at the end, where in runs *WITH* segfaults, the ERROR line is missing. (This only applies to the shutdown-segfault cases.)
(... many lines cut out ...) 00:02:21.600 * End of statistics 00:02:22.186 Changing the VM state from 'DESTROYING' to 'TERMINATED'. 00:02:22.299 vboxClipboardDestroy: shutting down host clipboard 00:02:22.300 vboxClipboardThread: clipboard thread terminated successfully with return code VINF_SUCCESS 00:02:22.630 ERROR [COM]: aRC=0x8000ffff aIID={09789f63-4525-48e5-a5e4-1080453b0eab} aComponent={Display} aText={The object is not ready} aPreserve=false
