Open Bug 1013737 Opened 10 years ago Updated 2 years ago

New google maps - black screen reports in lite mode

Categories

(Core :: Graphics: Canvas2D, defect)

29 Branch
x86
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: mpd, Unassigned)

References

()

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.131 Safari/537.36

Steps to reproduce:

We are getting lots of reports from FF/Linux users about black screens in lite mode of the new Google Maps. Our QA team was able to repro the problem, their report is as follows:

"Repro Steps: 1) google.com/maps/preview?force=canvas
                   2) Open the Runway
                   3) Select different thumbnails from the runway as fast as you can. Also when switching between different thumbnails try to click on the pegman once and get back to thumbnails."

I would love help debugging this; I realize there's no lost context API for 2D canvas, but if there's something we can do to prevent it that would be great.

The runway is the zippy in the lower-right that expands to show a selection of imagery.


Actual results:

Users are getting black screens.


Expected results:

No black screens.
Component: Untriaged → Canvas: 2D
OS: Mac OS X → Linux
Product: Firefox → Core
NI?milan for an owner.
Flags: needinfo?(milan)
Black screen, as in "it shows up black, then eventually it shows the image"?  Or black screen as in "it shows up black, and it stays black?"

Is this a regression?  If yes, any chance to get a range?
Flags: needinfo?(milan)
The background stays black after switching between pegman and thumbnails with versions as old as 2013-07-01 Nightly, at least.  A 2013-05-13 Nightly is redirected to classic maps.
I believe we send <27 to classic maps because of reports of instability. We can probably add a way to force to the new maps if you want to bisect, but this may not be a regression. We recently started defaulting Linux users to the new maps, so we're getting a large number of reports, but this might not be a new problem.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.