Fill layers don't render on some devices

[ljbade]

I just noticed today that on my Windows 8.1 machine random tiles are rendered blank.

The tiles jump around a bit as I zoom in and out.

I am using Chrome 39.0.2171.95 m

My machine has both Intel and NVIDIA graphics (not sure which one is used by Chrome).

[ansis]

Any errors in the console?

My guess would be network errors. If it fails to download a tile it just doesn't show anything. Should it do something different when downloads fail?

[ljbade]

@ansis no console errors.

Also I don't think it is download error as native has no issue on this computer and is very repeatable.

[ljbade]

Tested Windows Firefox, same problem.

Can't test on IE.

Doesn't happen with either Chrome or Firefox on my Linux machine.

[jfirebaugh]

@ljbade Is this still reproducible with 0.8.1?

[glennerichall]

I don't know if this is the same error, mapbox-gl works correctly with Chrome and Firefox on Linux but seems to be broken on Chrome and Firefox on Windows 7. Internet Explorer seems ok on Windows 7. Looks like only certain layers not visible, on the Mapbox example page and on my application.
Chrome Version 43.0.2357.130 m
Firefox Version 34.0.5
Note my app uses ver. 8.1:

Here are some screenshots
Internet Explorer:

Chrome, Firefox:

[ansis]

@glennerichall are there any errors logged in the firefox and chrome consoles?

[glennerichall]

Chrome and Firefox:
https://www.mapbox.com/core/api/session?_=1435670953287 Failed to load resource: the server responded with a status of 403 (Forbidden)

[lsimkins]

+1 on this issue. Several of our clients are experiencing the same thing. We currently embed Mapbox inside a .NET client app using Chromium Embedded Framework v39.0.1 which uses Chromium 39.0 under the hood. Every client using Windows 7 is experiencing the same issue.

Windows 7 using CEFv39.0.1 & Chromium 39.0

Chrome on OSX (No embed, just in browser)

I haven't seen this issue first-hand yet and only have screenshots. I'll take a look in the console to try and get more information.

[lsimkins]

Just to add additional information that may be relevant to troubleshooting this issue.

Initially the problem was sporadic and we were not able to replicate the issue in-house using CEFv39.0.1 on Windows 7. (CEF being Chromium Embedded Framework) MapboxGL worked perfectly.

Recently we updated CEF to v43 and suddenly we could reproduce the bug. I also noticed dropped tiles in the GL examples at https://www.mapbox.com/mapbox-gl-js/examples/.

We were only able to reproduce the issues in the more recent version of Chromium.

[Phrogz]

Not sure if this is the same core issue or a different one. I've been seeing problems where some of the the background colors of various styles is different per tile. For example, from "A simple map" (make sure you click on "A simple map") I see this:

This broken result is consistent for me across Chrome (v45.0.2454.101m), Firefox (v41.0) and IE (v11) on Windows 7x64 with a GeForce GTX 670 graphics card and the current driver (v355.82, released 2015-Aug-31).

[ljbade]

@jfirebaugh Do we have a Windows 7 machine we can repro this on?

[jfirebaugh]

At one point we had a floating Windows laptop in SF. Not sure if we still do. My first step for Windows or IE specific issues is https://github.com/xdissent/ievms.

[Phrogz]

I don't know if you updated code on the back-end, or if the Windows 7 SP1 update that I applied yesterday changed something (I suspect the former) but this morning the "simple map" works correctly across all browsers.

[lucaswoj]

I am unable to reproduce this bug in any combination of (Firefox, Chrome, IE) x (master, v0.11) on a Dell XPS 9Q33 running Windows 8.1. I will try to get a Windows 7 test environment set up next.

[lucaswoj]

I am further unable to reproduce this bug in a Windows 7 VM running on OS X in any of (Firefox, Chrome, IE).

[lucaswoj]

@ljbade @lsimkins @glennerichall Are you seeing this issue resolved, like @Phrogz in #930 (comment)? Also, what type of graphics card are you using?

[lucaswoj]

@fnicollet Have you ever seen this bug?

[fnicollet]

It reminds me of #1074, which I reproduced in Firefox a long time ago. I don't have Firefox installed anymore but I can give it a go if you want

[wilhelmberg]

I checked https://www.mapbox.com/mapbox-gl-js/examples/

W7, FF 41.0.1 ✅ looks good, no missing tiles

---

W7, Chrome 45.0.2454.101m ✅ looks good, no missing tiles

---

W8.1, Chrome 45.0.2454.101m, but I see the spinning cube, when I go to get.webgl.org:

---

W10: Chrome 45.0.2454.101m (don't see the cube) no Rats! message, just:

---

W10, Edge 20.10240.16384.0 (I see spinning cube):

[lucaswoj]

Thanks @BergWerkGIS!

Were "W8.1, Chrome 45.0.2454.101m" and "W10: Chrome 45.0.2454.101m" in a VM?

Unfortunately, Edge is quite broken right now. As I understand it, this is due to bugs in Edge's WebGL implementation and will be fixed in a future release. Tracking at #1437.

[wilhelmberg]

@lucaswoj
W8.1: MacBook Pro 13"
W10: VmWare Workstation Pro 12

[lucaswoj]

@BergWerkGIS There's a separate bug here which is that some systems, including "W8.1 + Chrome 45.0.2454.101m" and "W10 + Chrome 45.0.2454.101m" incorrectly indicate that WebGL is not supported. I will ticket that out.

Nobody is seeing random blank tiles as of GL JS v0.11.1?

[ljbade]

I no longer have a Windows 7 laptop, but this laptop had an NVIDIA GPU.

[wilhelmberg]

Tried again with "W8.1 + Chrome 45.0.2454.101m":

• now it works, no error message
• don't see any blank tiles
• but see things like these:

[fnicollet]

Hello @BergWerkGIS , this is a known issue of mapbox-gl-js:
#757
Been there since the beginning of mapbox-gl-js but the fix is blocked by some other issues in other projects

Fabien

[lucaswoj]

Based on the screenshots posted in this thread, it looks like there are a few different bugs being discussed. The main issue, as screenshot-ed in #930 (comment), is that our fill shaders do not work on some systems. There is an effort underway to refactor how our fill shaders work in #1606.

I can confirm that this bug can be reproduced on a Nexus 6 and that #1606 resolves the issue.

[lsimkins]

Just tested #1606 today and can confirm that it fixes all rendering issues we saw.

Any news on when #1606 will be merged? We're releasing a new version of our product next week that fully replaces Google Earth with mb-gl, and a few of our clients are running into the rendering issue.

Also - thank you!

[appgeodata]

[appgeodata]

I am in a MapBox workshop and using Google on Windows and getting totally hosed on getting started. Dane Springmeier giving me direction on how to report this problem:
Version 50.0.2661.75 m - Windows 7 Service Pack 1.

[mourner]

Should be fixed by #1606 which was merged to master, to be included in the next release.