Opened 12 years ago
Closed 12 years ago
#12111 closed defect (fixed)
Consistent VM Crash While Using Firefox
Reported by: | Adjutor | Owned by: | |
---|---|---|---|
Component: | 3D support | Version: | VirtualBox 4.2.18 |
Keywords: | Direct3D | Cc: | |
Guest type: | Windows | Host type: | Windows |
Description
Hi there,
I've used VirtualBox for several years now and have never noticed a bug like this. When I upgraded to latest version of VirtualBox, 4.2.18, I noticed a particular page that I was on crashed the VM immediately. I then quickly restarted the VM and noticed the same problem occurred when navigating to a particular page. I then opened up Portable Firefox to see if the problem was only with my installed version of Firefox. I found that the crash still occurred with different instance. To eliminate the possibility that the VM itself had a problem, I installed a new, fresh VM with same OS as the previous VM. After freshly installing the OS, I installed a fresh copy of Firefox. I then proceeded to install Adobe Flash Player as the particular page in question requires. I then navigated to the page and noticed that the VM did NOT crash. This was before Guest Additions was installed. I then restarted the VM in Safe Mode and installed Guest Additions WITHOUT Direct3D Experimental support. At this point, I turned on 3D Hardware Acceleration to see if this setting without Direct3D enabled effected anything. I then restarted the VM, opened Firefox, and navigated to the page in question. The VM did NOT crash. I then restarted the VM in Safe Mode and installed Guest Additions WITH Direct3D Experimental support. I restarted the VM, opened Firefox, and navigated to the page in question. The VM DID crash. The problem I see with this particular bug is how devastating it is from merely a browser, causing the entire VM to crash. I also did not notice this behavior in the previous VirtualBox release (4.2.16). I believe one of the new changes is the source of this crash. I believe the crash is caused by 3D support.
So, to reproduce this behavior:
- Create new Windows XP VM, put 3D Acceleration on to 128MB
- Install Firefox in the VM
- Install Adobe Flash Player in the VM
- Install VirtualBox Guest Additions with 3D support
- Navigate to "Testing Webpage" using Firefox
Note: if the VM does not crash immediately, I noticed in combination with scrolling that page and/or waiting a minute will cause it to crash.
Host OS: Windows 7 Professional x64 with SP1 Guest OS: Windows XP Professional with x86 with SP3 Testing Webpage: http://flashvideotrainingsource.com/featured_post/hints-and-tips/build-a-stage3d-shoot-em-up-explosions-parallax-and-collisions
Windows Problem Signature: Problem signature:
Problem Event Name: APPCRASH Application Name: VirtualBox.exe Application Version: 4.2.18.0 Application Timestamp: 5229ca20 Fault Module Name: nvoglv64.DLL Fault Module Version: 9.18.13.1106 Fault Module Timestamp: 50f947d1 Exception Code: c0000005 Exception Offset: 0000000000851e80 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 6b9c Additional Information 2: 6b9c85f1389b2d9c44f162c847f67bfd Additional Information 3: 3281 Additional Information 4: 3281c956c43b72d25d9425966f2d08f6
I have attached the VBox.log. Please let me know if someone can reproduce this issue.
Thank you.
Attachments (1)
Change History (3)
by , 12 years ago
comment:1 by , 12 years ago
I am unable to reproduce this issue with the latest test VBox build. It is very likely that your issue is solved already with VBox ?post-?4.3 changes.
Could you try the following test build that has all fixes included:
Windows Host:
http://www.virtualbox.org/download/testcase/VirtualBox-4.3.1-90291-Win.exe
Extension Pack:
http://www.virtualbox.org/download/testcase/Oracle_VM_VirtualBox_Extension_Pack-4.3.1-90291.vbox-extpack
NOTE that you'll need to update Guest Additions to those supplied with the build.
Let me know if you need a build for any other host OS type.
comment:2 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if still relevant with VBox 4.3.2. If you still experience this problem, please attach a VBox.log file from such a VBox 4.3.2 VM session.
VBox.log