Closed
Bug 1037230
Opened 10 years ago
Closed 10 years ago
Graphics glitch and crash when opening Bing Maps
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1049450
People
(Reporter: josh.tumath+bugzilla, Unassigned)
References
()
Details
(Keywords: crash)
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 (Beta/Release) Build ID: 20140710030200 Steps to reproduce: When opening Bing Maps, areas of the window become black, followed quickly by a crash. bp-3825bc89-7826-4bfd-85fc-f89552140710
Reporter | ||
Updated•10 years ago
|
Severity: normal → critical
Comment 1•10 years ago
|
||
Can you send in the graphics section of about:support?
I'm also seeing this OOM (bug 1028491 comment 14). It puzzles me that this is so reproducible even on a fresh launch when I have the entire address space available. Can we trust the OOM size annotation? 16k makes no sense. Graphics Adapter Description Intel(R) HD Graphics 5000 Adapter Drivers igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32 Adapter RAM Unknown ClearType Parameters Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 100 Device ID 0x0a26 Direct2D Enabled true DirectWrite Enabled true (6.3.9600.17111) Driver Date 5-16-2014 Driver Version 10.18.10.3621 GPU #2 Active false GPU Accelerated Windows 1/1 Direct3D 11 (OMTC) Vendor ID 0x8086 WebGL Renderer Google Inc. -- ANGLE (Intel(R) HD Graphics 5000 Direct3D9Ex vs_3_0 ps_3_0) windowLayerManagerRemote true AzureCanvasBackend direct2d AzureContentBackend direct2d AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0
Status: UNCONFIRMED → NEW
Ever confirmed: true
Josh can you try Bing Maps again on the latest Nightly or Aurora? For me it seems to have been fixed by bug 1046528.
Flags: needinfo?(josh)
Reporter | ||
Comment 4•10 years ago
|
||
Yep. I can confirm it's fixed.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(josh)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•