User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64 Safari/537.11 Steps to reproduce: OS: xp Graphic Card: Geforce 6600 GT 1- open firefox, empty cache and open http://maps.google.com 2- enable mapsGL 3- start the guided tour Actual results: many different issues, most common are map scambles and sometimes browser crashes immediately. Expected results: able to complete tour and no crashes. May need to black list webGL for graphic card.
I'm not sure from comment 0 if this is on Linux or on Windows XP? I assume Windows XP from "OS: xp". What driver version is this with? Need QA to reproduce this bug. If it reproduces consistently, we should blacklist the affected driver versions on this device for WebGL. I would also be interested in knowing if this bug is specific to this single device (6600 GT) or reproduce on other Geforce 6 series devices.
Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/19.0 Firefox/19.0 Graphic card: GeForce 8400 GS/PCIe/SSE2 Graphics(from about:support): Adapter Description: nouveau -- Gallium 0.4 on NV98 Device ID: Gallium 0.4 on NV98 Driver Version: 2.1 Mesa 8.0.2 GPU Accelerated Windows: 0/1 Basic Vendor ID: nouveauWebGL Renderer: nouveau -- Gallium 0.4 on NV98 I tried to reproduce the issues described on Ubuntu 12.04 x64 and I got these: - in photo tours - images are not rendered correctly (a sort of black and white very blurred image, nothing visually understandable) - sometimes map is not rendered (after entering/exiting street view mode), it displays only white/grey background Although in street view mode I got some hangs and very jerky navigation (after navigating for about 10 minutes, with memory continuously increasing to more than 2GB), I could not crash. For Windows systems there are a few bugs logged on crashes reproducible in Google maps with WebGl enabled: see bug #791999, bug 793126 and bug #790473. bjacob, is there anything else you need qa help with on this issue?
Hi, we are still seeing the same issue with Firefox 18.0.2 We are running on Nvidia with driver version 220.127.116.111 (date 9/23/2012) GeForce 66000 GT with Windows XP
Please let me know if you need more info.
So, rereading this bug: Comment 2 was testing linux, but although comment 0 was confusing, comment 3 and 4 make it clear that the report is about winxp, not linux. @DChan: please paste a copy of about:support Graphics next time on the config that reproduce, so we avoid these misunderstandings in the future. @DChan: would you by chance know what user-facing driver version (5 digits, e.g. "295.89") the internal DLL version in comment 3 corresponds to? @Mihaela: can you reproduce this on WinXP with the driver version mentioned in comment 3?
Component: Graphics → Canvas: WebGL
about:support return the following: Adapter Description NVIDIA GeForce 6800 Series GPU Adapter Drivers nv4_disp Adapter RAM Unknown Device ID 0x00f9 Direct2D Enabled no information DirectWrite Enabled false (0.0.0.0) Driver Date 1-3-2013 Driver Version 18.104.22.1684 The version is not xxx.xx format.
Thanks for the detailed version info now. This driver version 22.214.171.1244 seems to be driver 307.74. Indeed the xxx.xx driver version is just the last 5 digits of the DLL version and 774 is 0774 without the leading 0. So that's a really recent driver, as the 'Driver Date' in comment 6 confirms. Do you think that this bug applies to all driver versions? Or is it a regression of newer drivers on older cards? Also, there is a discrepancy between the title of this bug (which says Geforce 6600 GT) and comment 6 (which says Geforce 6800). Which one does reproduce the bug you're reporting? I searched our crash database for people with the device ID in comment 6 (0x00f9, Geforce 6800) and only 1 in 30,000 Windows XP Firefox users have this particular GPU. The figure is similar on other Windows versions. So a blacklist rule for specifically for it would not have a very significant impact on our user base.
I'm sorry for the confusion. It looks as if I uploaded the incorrect about:support file into the bug report on Friday. The 6800 file was for a different bug. This issue occurs on the NVIDIA GeForce 6600 GT. The manufacturer's package number that is at the beginning of the file name of the driver file installed is 306.81 about:support return the following: Adapter Description NVIDIA GeForce 6600 Adapter Drivers nv4_disp Adapter RAM Unknown Device ID 0x0141 Direct2D Enabled no information DirectWrite Enabled false (0.0.0.0) Driver Date 1-3-2013 Driver Version 126.96.36.1994
When doing compatibility testing, we typically use the latest drivers available. We have not tested using older drivers. dchan, would you like me to perform a test with this card using older drivers to see if this is a regression due to newer drivers on an older card? If so, back would you like me to go? (In reply to Benoit Jacob [:bjacob] from comment #7) > Do you think that this bug applies to all driver versions? Or is it a > regression of newer drivers on older cards?
> @Mihaela: can you reproduce this on WinXP with the driver version mentioned > in comment 3? I could not find that diver version (188.8.131.521) for Ubuntu, I think it's XP only.
Removing qawanted keyword. Please re-add it if there is anything else QA can help with.
I can't find a way to enable mapsGL. Can you repro again and write down the exact steps?
You need to log in before you can comment on or make changes to this bug.