Opened 16 years ago
Closed 15 years ago
#3366 closed defect (fixed)
memory access violation after guest shutdown
Reported by: | Markus Elfring | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 2.1.4 |
Keywords: | memory access | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description
I have installed the current software release. I have tried to look at the guest "Knoppix 5.3.1" on my Windows XP (SP 3) system. It worked fine during my short test until a problem with memory access was reported at the end of the shutdown for the virtual machine.
Ereignistyp: Informationen Ereignisquelle: Application Popup Ereigniskategorie: Keine Ereigniskennung: 26 Datum: 17.02.2009 Zeit: 22:16:23 Benutzer: Nicht zutreffend Computer: SONNE Beschreibung: Anwendungspopup: VirtualBox.exe - Fehler in Anwendung: Die Anweisung in "0x02f333b8" verweist auf Speicher in "0x02f333b8". Der Vorgang "read" konnte nicht auf dem Speicher durchgeführt werden.
Attachments (1)
Change History (5)
by , 16 years ago
comment:1 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if this problem persists with VirtualBox 2.2.2.
comment:2 by , 16 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
It has happened again.
Ereignistyp: Informationen Ereignisquelle: Application Popup Ereigniskategorie: Keine Ereigniskennung: 26 Datum: 01.05.2009 Zeit: 20:46:30 Benutzer: Nicht zutreffend Computer: SONNE Beschreibung: Anwendungspopup: VirtualBox.exe - Fehler in Anwendung: Die Anweisung in "0x02e233b5" verweist auf Speicher in "0x02e233b5". Der Vorgang "read" konnte nicht auf dem Speicher durchgeführt werden.
comment:3 by , 15 years ago
I can not reproduce the read error with VirtualBox version 3.0.0 r49315 at the end.
(Now the program "KDesktop" crashes because of the signal "SIGABRT" at the beginning of the graphical Knoppix 5.3.1 session.)
comment:4 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
The KDesktop problem might be fixed in a later VBox 3.0.x release, therefore I will close this bug.
log file