VirtualBox

Opened 10 years ago

Closed 9 years ago

#12772 closed defect (fixed)

3D Accelerated Linux Guests Crash on Shutdown

Reported by: h-w Owned by:
Component: 3D support Version: VirtualBox 4.3.8
Keywords: 3D Shutdown 0xc0000005 Cc:
Guest type: Linux Host type: Windows

Description

3D enabled 64-bit Ubuntu and Fedora guests crash on shutdown. In the log file (attached) the log reaches the line:

Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)

Then a Windows exception code 0xc0000005 occurs.

The host is an Asus M5A97 EVO with a Phenom II X4 810 CPU, ATI HD 4850 GPU, 16GB RAM running 64-bit Vista Home Premium, service pack 2, and all updates.

Guests are all updated as of 4 March 2014. Guests which crash include Fedora 19 and 20, Ubuntu 12.04 and 13.10. Guest additions were built on the VMs but I don't think they have an impact on the problem.

Guests do not crash every time they are shutdown. The Fedora 20 seems to crash almost every time.

Virtual Box is run under a regular user with no Administrator rights.

The problem occurs on both pre-existing VMs which worked fine under 4.3.6 and on newly created VMs. I created a new Fedora 20 VM under a user which had not run VirtualBox before, so all user files and configuration were created by 4.3.8. The VM was created as a Fedora 20 desktop system, no LibreOffice, added packages: kernel-headers, kernel-devel, gcc, make, dkms, vim-minimal, vim-enhanced, tcsh, xterm, git-all to enable building and installing guest additions and investigating the problem.

I've attached the user configuration file, copies of the errors reported by eventvwr, and showvminfo dumps for working and crashing configurations.

Attachments (10)

VBox.log (78.8 KB ) - added by h-w 10 years ago.
Log file showing crash on shutdown
VBox.log.1 (80.5 KB ) - added by h-w 10 years ago.
Log file showing successful shutdown (3D disabled)
showvminfo.txt (7.1 KB ) - added by h-w 10 years ago.
showvminfo for working and crashing VM (3d setting diff)
Eventviewer-error.txt (2.6 KB ) - added by h-w 10 years ago.
Errors from eventvwr
VirtualBox.xml (1.8 KB ) - added by h-w 10 years ago.
user configuration
VirtualBox.exe.4412.dmp_split.gz_aa (400.0 KB ) - added by h-w 10 years ago.
Minidump from 12 May 2014 (VBox 4.3.10 r93012) Part a
VirtualBox.exe.4412.dmp_split.gz_ab (400.0 KB ) - added by h-w 10 years ago.
Minidump from 12 May 2014 (VBox 4.3.10 r93012) Part b
VirtualBox.exe.4412.dmp_split.gz_ac (167.1 KB ) - added by h-w 10 years ago.
Minidump from 12 May 2014 (VBox 4.3.10 r93012) Part c
event-viewer-error-12-may-2014.txt (1.3 KB ) - added by h-w 10 years ago.
Event Viewer Error for 12 May 2014 Minidump
VBox_Mint.log (98.6 KB ) - added by VickersNick 10 years ago.
Log from 4.3.17 Test Build

Download all attachments as: .zip

Change History (45)

by h-w, 10 years ago

Attachment: VBox.log added

Log file showing crash on shutdown

by h-w, 10 years ago

Attachment: VBox.log.1 added

Log file showing successful shutdown (3D disabled)

by h-w, 10 years ago

Attachment: showvminfo.txt added

showvminfo for working and crashing VM (3d setting diff)

by h-w, 10 years ago

Attachment: Eventviewer-error.txt added

Errors from eventvwr

by h-w, 10 years ago

Attachment: VirtualBox.xml added

user configuration

comment:1 by h-w, 10 years ago

After some experimentation, the problem seems to be the same with 4.3.10.

comment:2 by misha, 10 years ago

Could you create and attach a minidump for the crash? See http://msdn.microsoft.com/en-us/library/bb787181%28VS.85%29.aspx on how to enable it.
Using default values mentioned there is sufficient, so just creating a HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps registry key should be enough to enable dump generation.

comment:3 by misha, 10 years ago

Component: other3D support

comment:4 by bbhar, 10 years ago

Same thing happend to me in VirtualBox 4.3.8 and 4.3.10 when 3D support in enabled for 64bit linux geusts - Ubuntu 13.10, Ubuntu 14.04, Linux Mint 16 and Oracle Enterprise Linux 6 Update 5. Switched back to VirtualBox 4.3.6 and 3D support is Ok.

My host is Windows 7 64 bit Home Edition on Dell Inspiron 14z 5423 with 8GB RAM.

by h-w, 10 years ago

Minidump from 12 May 2014 (VBox 4.3.10 r93012) Part a

by h-w, 10 years ago

Minidump from 12 May 2014 (VBox 4.3.10 r93012) Part b

by h-w, 10 years ago

Minidump from 12 May 2014 (VBox 4.3.10 r93012) Part c

by h-w, 10 years ago

Event Viewer Error for 12 May 2014 Minidump

comment:5 by h-w, 10 years ago

Attached minidump from 12 May 2014 and corresponding error from Event Viewer. Sorry, it's in 3 parts due to upload size restrictions. You put it back together (on Cygwin in my case, but any cat + gunzip should work) using:

cat VirtualBox.exe.4412.dmp_split.gz_* | gunzip -c > VirtualBox.exe.4412.dmp

comment:6 by Mihai Hanor, 10 years ago

I can always reproduce a crash in atio6axx.dll, when saving the VM state, but it might be a bug in the AMD drivers. atio6axx code crashes when accessing a heap memory location, freed by atio6axx, during the deletion of the OpenGL rendering context. It was allocated by atio6axx when the OpenGL rendering context was created.

comment:7 by h-w, 10 years ago

I'm running Catalyst 13.9 Driver Pkg 8.97.100.11-130429a-158498C-ATI which is the last legacy support driver. I'd really appreciate a work-around if possible as I suspect a fix from AMD/ATI is unlikely. If the problem can be traced to the AMD driver I'd be happy to open a ticket with them, but they would need documentation on how to reproduce the error, even then, this is legacy H/W.

comment:8 by TimOr, 10 years ago

Same for me. I'm on Windows 7 SP1 x64. VB is 4.3.10, but I think it started with 4.3.8. Fedora 20 with kernel 3.13 or 3.14 seems to crash almost every time, LMDE with kernel 3.11-2 sometimes.

APPCRASH

Application Name: VirtualBox.exe Application Version: 4.3.10.0 Application Timestamp: 533315cb Fault Module Name: atio6axx.dll Fault Module Version: 6.14.10.12217 Fault Module Timestamp: 5154f6b2 Exception Code: c0000005 Exception Offset: 0000000000b4e343 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 4122 Additional Information 1: ac1e Additional Information 2: ac1ee5ba95997c124f29eccdf6034af4 Additional Information 3: 5a7b Additional Information 4: 5a7b44b651fc1abf0447ccd270cea49e

These are similar reports, probably duplicates: https://www.virtualbox.org/ticket/12904, https://www.virtualbox.org/ticket/12953, https://www.virtualbox.org/ticket/12968.

comment:9 by h-w, 10 years ago

Problem persists in VirtualBox-4.3.12-93733-Win. Minidump available on request.

comment:10 by bartsblues, 10 years ago

I can also confirm the above:

1)Windows 7 x64 host

2)Ubuntu 14.04 Release (Although I got the same error with 13.10 as well)

3)VirtualBox 4.3.12 with guest additions

Attempted complete removal and reinstall of AMD drivers to no effect.

comment:11 by Bloodtoes, 10 years ago

Also ocurring here.

Software: Oracle VM VirtualBox 4.3.10 r93012

HOST INFO

OS: Windows 8.1 Professional x64
Video: AMD Radeon HD 7970
Video Driver Version: 13.512.1.8-131008a-163824C-ATI

GUEST INFO

Linux Mint 17 "Quiana" Cinnamon RC x64 (based on Ubuntu 14.04)
Linux Ubuntu (64 bit) virtual machine options used.
3D Acceleration Enabled
128 MB Video Memory

No crash on shutdown if I disable 3D acceleration. I will look at updating both VirtualBox and video drivers.

Last edited 10 years ago by Bloodtoes (previous) (diff)

comment:12 by trenzterra, 10 years ago

Hi, I have the exact same issue. I tried installing the latest Catalyst 14.4 drivers but it still happens.

comment:13 by Low351, 10 years ago

Same issue latest version of VirtualBox, 3D acceleration and AMD drivers on win7 64bit.

comment:14 by Mihai Hanor, 10 years ago

The crash occurs every time at VM shutdown, if you ever triggered a screenshot by: pausing the VM, manually taking a screenshot or even by the VirtualBox Manager (for the VM preview), while the guest additions were started (with Ubuntu, they are started after you login). At the moment of the crash, which occurs in atio6axx, during the release of the OpenGL context, there are heap resources (found by inspecting the CPU registers at the crash location) that seem to never get freed (not even if you reboot the VM). These heap resources were allocated in the following contexts:

Call stack 1 (during BindBufferARB() ):

...
atio6axx!...
VBoxOGLhostcrutil!crTdBltCheckPBO+0xaf [c:\work_x64\vbox\src\vbox\guesthost\opengl\util\blitter.cpp @ 1376]
VBoxOGLhostcrutil!CrTdBltDataAcquire+0x198 [c:\work_x64\vbox\src\vbox\guesthost\opengl\util\blitter.cpp @ 1704]
VBoxSharedCrOpenGL!CrFbBltGetContents+0x580 [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserverlib\server_presenter.cpp @ 676]
VBoxSharedCrOpenGL!CrFbBltGetContentsEx+0xd8 [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserverlib\server_presenter.cpp @ 752]
VBoxSharedCrOpenGL!crServerVBoxScreenshotGet+0x287 [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserverlib\server_muralfbo.cpp @ 703]
VBoxSharedCrOpenGL!crScreenshotHandle+0xb7 [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserver\crservice.cpp @ 993]
VBoxSharedCrOpenGL!svcHostCallPerform+0x1484 [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserver\crservice.cpp @ 1308]
VBoxSharedCrOpenGL!crVBoxServerHostCtl+0x8e [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserver\crservice.cpp @ 1537]
VBoxSharedCrOpenGL!svcHostCall+0x11d [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserver\crservice.cpp @ 1568]
VBoxC!hgcmServiceThread+0x19e [c:\work_x64\vbox\src\vbox\main\src-client\hgcm.cpp @ 536]
VBoxC!hgcmWorkerThreadFunc+0xf9 [c:\work_x64\vbox\src\vbox\main\src-client\hgcmthread.cpp @ 196]
VBoxRT!rtThreadMain+0xc2 [c:\work_x64\vbox\src\vbox\runtime\common\misc\thread.cpp @ 712]
VBoxRT!rtThreadNativeMain+0xae [c:\work_x64\vbox\src\vbox\runtime\r3\win\thread-win.cpp @ 211]
MSVCR100!endthreadex+0x0000000000000043
MSVCR100!endthreadex+0x00000000000000df
kernel32!BaseThreadInitThunk+0x000000000000000d
ntdll!RtlUserThreadStart+0x000000000000001d

Call stack 2 (during MapBufferARB() ):

...
atio6axx!...
VBoxOGLhostcrutil!crTdBltImgAcquire+0x21f [c:\work_x64\vbox\src\vbox\guesthost\opengl\util\blitter.cpp @ 1506]
VBoxOGLhostcrutil!CrTdBltDataAcquire+0x2ff [c:\work_x64\vbox\src\vbox\guesthost\opengl\util\blitter.cpp @ 1732]
VBoxSharedCrOpenGL!CrFbBltGetContents+0x580 [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserverlib\server_presenter.cpp @ 676]
VBoxSharedCrOpenGL!CrFbBltGetContentsEx+0xd8 [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserverlib\server_presenter.cpp @ 752]
VBoxSharedCrOpenGL!crServerVBoxScreenshotGet+0x287 [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserverlib\server_muralfbo.cpp @ 703]
VBoxSharedCrOpenGL!crScreenshotHandle+0xb7 [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserver\crservice.cpp @ 993]
VBoxSharedCrOpenGL!svcHostCallPerform+0x1484 [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserver\crservice.cpp @ 1308]
VBoxSharedCrOpenGL!crVBoxServerHostCtl+0x8e [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserver\crservice.cpp @ 1537]
VBoxSharedCrOpenGL!svcHostCall+0x11d [c:\work_x64\vbox\src\vbox\hostservices\sharedopengl\crserver\crservice.cpp @ 1568]
VBoxC!hgcmServiceThread+0x19e [c:\work_x64\vbox\src\vbox\main\src-client\hgcm.cpp @ 536]
VBoxC!hgcmWorkerThreadFunc+0xf9 [c:\work_x64\vbox\src\vbox\main\src-client\hgcmthread.cpp @ 196]
VBoxRT!rtThreadMain+0xc2 [c:\work_x64\vbox\src\vbox\runtime\common\misc\thread.cpp @ 712]
VBoxRT!rtThreadNativeMain+0xae [c:\work_x64\vbox\src\vbox\runtime\r3\win\thread-win.cpp @ 211]
MSVCR100!endthreadex+0x0000000000000043
MSVCR100!endthreadex+0x00000000000000df
kernel32!BaseThreadInitThunk+0x000000000000000d
ntdll!RtlUserThreadStart+0x000000000000001d

Maybe VirtualBox isn't cleaning up properly after crServerVBoxScreenshotGet/CrFbBltGetContents/CrFbBltGetContentsEx. The call stacks are for VirtualBox 4.3.14 OSE (no hardening).

Last edited 9 years ago by Mihai Hanor (previous) (diff)

comment:15 by Mihai Hanor, 10 years ago

By adding a call to CrTdBltDataCleanup(pTex), after CrTdBltDataRelease(pTex), inside CrFbBltGetContents(), it doesn't crash anymore, at shutdown.

Last edited 10 years ago by Mihai Hanor (previous) (diff)

comment:16 by h-w, 10 years ago

Problem persists in VirtualBox-4.3.15-95286-Win. Minidump and logs available on request. I was unable to get VirtualBox-4.3.14-95030-Win to run. I'm willing to run a test version with mhanor's suggested change (above) if that would be useful. Just provide me with a download link.

Best Rgds, -H-

Last edited 10 years ago by h-w (previous) (diff)

comment:17 by TimOr, 10 years ago

I also was unable to get VirtualBox-4.3.14-95030-Win to run. Testing with 4.3.15, 3D seems to work now. But, crashes now are regular, unlike before when they were accidental. For some reason, I couldn't get 3D to work in Ubuntu 14.04 x64, kernel 3.13.0-34-generic, but it shuts down fine. 3D works in my Mint 17 x64, kernel 3.13.0-24, but I get a crash on shutdown. 3D works in my Fedora 20 x64, kernle 3.15.10, but I get a crash on shutdown. Reported in https://forums.virtualbox.org/viewtopic.php?f=6&t=62615&p=297643#p297643

comment:19 by sickle, 10 years ago

I have the same problem. VirtualBox 4.3.12 on Windows 7 64 bits. I'm also running the VM with 3D enabled. The guest operating system is Mint 17 64 bits.

comment:20 by VickersNick, 10 years ago

I have the same issue on Win 7 32 bit Host, Mint 17 32 bit guest running with VB test build 4.3.17r96235 and 4.3.17r96164 GA iso. My guest crashes every time though. If I disable 3D Acceleration it shuts down normally.

As an aside, I'm also seeing the following. Not sure if it's related.

/usr/lib/nux/unity_support_test -p
libGL error: pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo

by VickersNick, 10 years ago

Attachment: VBox_Mint.log added

Log from 4.3.17 Test Build

comment:21 by TimOr, 10 years ago

Same problem in 4.3.18.

comment:22 by amenic, 9 years ago

This is still ... not... resolved after 8 months... It sounds like someone already posted the solution above...

By adding a call to CrTdBltDataCleanup(pTex), after CrTdBltDataRelease(pTex), inside CrFbBltGetContents(), it doesn't crash anymore, at shutdown.

Can we not get this fix included on the next iteration of the vbox guest additions? 4.3.1x or 4.3.2x?

comment:23 by h-w, 9 years ago

Problem persists in VirtualBox-4.3.20-96996-Win.

comment:24 by DO, 9 years ago

Can be reproduced with 4.3.21-r97058 as well.

comment:25 by Mihai Hanor, 9 years ago

Possible duplicate bug: #13671

comment:26 by Jasona, 9 years ago

Identical behaviour. 3D Acceleration enabled causes repeatable crash.

Host: Windows 7 x64, AMD/ATI HD6850 graphics hardware, VirtualBox-4.3.20-96997-Win. Latest patches & guest additions.

Guest: Ubuntu 14.04 x64

Given cause seems to be known, let me know if dump or other diagnostics will be helpful.

comment:27 by Mihai Hanor, 9 years ago

Anyone affected by this issue, should also report it to AMD, http://www.amd.com/report

comment:28 by BitFlipper, 9 years ago

I believe I am experiencing the same problem with an Ubuntu 14.10 x64 VM on Windows 8.1 x64 with a Radeon 7950 Boost, latest Omega 14.12 drivers. Virtual Box 4.3.24 r98716 with latest guest additions.

With 3D acceleration turned off, the machine can save its state just fine, but that means the GUI becomes really slow, almost like using remote desktop & the CPU usage shoots way up.

VirtualBox.exe - Application Error The instruction at 0x629bc5dc referenced memory at 0x0ad19c40. The memory could not be read.

Failed to save the state of the virtual machine . Machine terminated with pending save state!.

Result Code: E_FAIL (0x80004005) Component: SessionMachine Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}

VirtualBox rocks, I hope you guys can fix this!

in reply to:  28 comment:29 by Erik99, 9 years ago

After upgrading from 4.3.22 to 4.3.26 and installing the corresponding guest additions the error returned Host Windows 7, guest Ubuntu 14.04 LTS. Seems a regression to me.

comment:30 by Subev, 9 years ago

I experience the same issue after I updated to use the latest version of virtualbox. Had no problem before that. When I disable 3D acceleration, save state or shutdown works as expected.

comment:31 by Frank Mehnert, 9 years ago

We hopefully fixed the problem. Could you test on of the most recent test builds?

comment:32 by Mihai Hanor, 9 years ago

The new build doesn't crash.

comment:33 by Frank Mehnert, 9 years ago

Thanks for testing!

in reply to:  33 comment:34 by Frumpasaurus, 9 years ago

Replying to frank:

We hopefully fixed the problem. Could you test on of the most recent test builds?

Issue seems to be fixed in 4.3.x revision 100276. Using Windows 10 as Host OS. Linux Mint 17.1 as the guest OS set as Ubuntu (32 bit).

comment:35 by Frank Mehnert, 9 years ago

Resolution: fixed
Status: newclosed

Fix is part of VBox 4.3.28.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use