1489436 - Firefox 62.0 shows black screen in baidu street maps

Status: NEW

(Core :: Graphics: CanvasWebGL, defect, P3)

Description

[zw]

Attachment: firefox62.png

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0
Build ID: 20180830143136

Steps to reproduce:

1、open map.baidu.com
2、choose street map, chinese named “全景”
3、click some point in blue area


Actual results:

I saw black sreen, before updating, baidu street map works well


Expected results:

It should show well

Comment 1

[Johann Hofmann [:johannh]]

Not a security bug

Comment 2

[zw]

(In reply to Johann Hofmann [:johannh] from comment #1)
> Not a security bug

Could you tell me, where should I post?

Comment 3

[Johann Hofmann [:johannh]]

(In reply to zw from comment #2)
> (In reply to Johann Hofmann [:johannh] from comment #1)
> > Not a security bug
> 
> Could you tell me, where should I post?

I'll move this to Canvas:WebGL since it seems they are using WebGL. From a quick try this works fine for me on Nightly, though.

Let's see what Graphics people say.

Thanks for the report!

Comment 4

[yxu]

Attachment: compared with Fx61 & Fx62

https://map.baidu.com/#panoid=0900220001150522062342789A6&panotype=street&heading=176.75&pitch=0&l=15&tn=B_NORMAL_MAP&sc=0&newmap=1&shareurl=1&pid=0900220001150522062342789A6

We can directly access this URL for testing. I just placed a coordinate point on the map.

This problem does exist and many people can reproduce it. It works fine on the 61 and nightly versions, and the 62 release version shows a black screen.

I haven't get any valid information from mozregression.

Comment 5

[[:philipp]]

i couldn't reproduce this with mozregression on nightly builds either. this regressed from 62.0b18 to 62.0b19 though, bugs with patches landing in that timeframe are here: https://mzl.la/2nT45IA
so i'm assuming this was another defect caused by bug 1477817.

since that got backed out from 62 we should already be good here for 62.0.2 and probably can close the bug after other affected users confirm that neither 64.0a1, 63.0b nor 62.0.2 (to be released in the coming days) show the buggy behaviour anymore.

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.