Opened 13 years ago
Closed 11 years ago
#9528 closed defect (fixed)
0xc0000005 Access Violation in VBoxSVC.exe during Delete Snapshot operation
Reported by: | Bob Kosch | Owned by: | |
---|---|---|---|
Component: | virtual disk | Version: | VirtualBox 4.1.2 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Windows |
Description (last modified by )
Happens with much less frequency than 4.1.0, where it was an everyday occurrence, but when VBoxSVC crashes in the middle of collapsing the state of the virtual machine, it invariably leaves orphaned files, resulting in the usual (2)-child hard stalemate.
Host is Windows 7 x64 SP1.
Attachments (6)
Change History (12)
by , 13 years ago
Attachment: | Event 1000, Application Error.txt added |
---|
by , 13 years ago
Attachment: | VBoxSVC.log added |
---|
by , 13 years ago
by , 13 years ago
Attachment: | VMM Screen Capture #1.PNG added |
---|
by , 13 years ago
Attachment: | VMM Screen Capture #2.PNG added |
---|
by , 13 years ago
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Another occurrence when reverting the current machine state to a previous snapshot.
This also results in the snapshot forking into multiple vdi files, thus being rendered undeletable.
The developers need to find their own ways of isolating instabilities in their hypervisor by exhaustive automated software testing, not insisting that end-users provide a precise sequence of replication steps, an approach which is a total dead-end, thus doomed to failure.
We are not resources for regression-testing VirtualBox, we need to concentrate on actually using it, confining our testing to the virtual environments themselves, not the virtualization environment.
Log Name: Application
Source: Application Error
Date: 9/17/2011 7:36:25 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: wrkosch
Description:
Faulting application name: VBoxSVC.exe, version: 4.1.2.0, time stamp: 0x4e4911e8
Faulting module name: VBoxSVC.exe, version: 4.1.2.0, time stamp: 0x4e4911e8
Exception code: 0xc0000005
Fault offset: 0x00000000001937a9
Faulting process id: 0x105c
Faulting application start time: 0x01cc7580a91ebead
Faulting application path: E:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
Faulting module path: E:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
Report Id: 004cc6e8-e19f-11e0-8c17-005056c00008
comment:3 by , 12 years ago
Reproduces in VirtualBox 4.1.10, while trying to delete a snapshot via VBoxManage.exe. Running Windows XP x86 SP3 guest on Windows 7 x64 SP1 host.
Faulting application name: VBoxSVC.exe, version: 4.1.10.0, time stamp: 0x4f60d450
Faulting module name: VBoxSVC.exe, version: 4.1.10.0, time stamp: 0x4f60d450
Exception code: 0xc0000005
Fault offset: 0x000000000014a9c4
...
Faulting application path: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
comment:4 by , 12 years ago
Call stack on ver 4.1.10:
VBoxSVC.exe+0x14a9c4
VBoxSVC.exe+0x19814a
VBoxSVC.exe+0x18c6b4
VBoxRT.dll!RTThreadFromNative+0x54f
VBoxRT.dll!RTSymlinkRead+0x30a
comment:6 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
The reporter answered by email that he did not experience this problem with VBox 4.2.0 so closing.
i have exactly the same!