1465980 - Google Maps Freezes

Status: UNCONFIRMED

(Core :: JavaScript Engine, defect, P3)

Description

[James]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180516032328

Steps to reproduce:

Went to Google Maps
Searched for a city (any city or state will suffice)


Actual results:

Google Maps went to that location, but then the cursor shape froze and the page was not responsive.


Expected results:

Google Maps should have behaved normally with full functionality.

Comment 1

[Timea Cernea [:tbabos][inactive]]

Hey James,

I didn’t manage to reproduce the freeze on the latest Firefox Nightly ((2018-06-04) and Firefox Release 60.0.1. on Windows 10 x64.

Does it freeze everytime you search a location in google maps or it is intermittent? If you can reproduce the issue on the latest Firefox Release 60.0.1. and latest Nightly 62.0a1. (2018-06-04) and the browser crashes afterwards, please submit the crash report and post the signature here. 

Consider retesting the issue using a new clean Firefox profile (https://goo.gl/AWo6h8) as well as safe mode (https://goo.gl/AR5o9d) to eliminate custom settings as a possible cause. Also you can check if there are any errors displayed in the browser console while the issue occurs.

Thank you for the report and hopefully we can sort it out.

Comment 2

[James]

This is a real puzzler.  I started Firefox in Safe Mode with all three of my addons disabled.  I could not reproduce the problem.  I then restarted Firefox normally and disabled all but one of the addons, testing each one.  I could not reproduce the problem.  However, with all three addons functioning, the problem persists.  Specifically, the problem is:
perform a Google search on any US street address.
in the search results, click on the Google Map image.
Once on the Google Map page, zoom in and try to move the map image around with the cursor and left-click.

This causes the map to "hang".  The addons are:
Video Download helper
LastPass
Awesome Screenshot Plus.

And I an running Firefox 60.0.1 (64-bit on Windows 10).

Comment 3

[Timea Cernea [:tbabos][inactive]]

Thank you for the response James. This indeed looks strange, however I didn't manage to reproduce the issue on the latest Nightly (2018-06-06) and Firefox Release 60.0.1.

I created a new/clean Firefox profile, installed only the 3 addons you mentioned, searched for 9th Ave street in google search, clicked on the Google Map image that lead me to the actual Google Map. It was a bit hanging for like 1 second until the map was loaded and afterwards I could zoom in and move the image around without any issue.

I'm not entirely sure if you also used a clean profile, since you only mentioned Safe Mode. Can your please retest the issue as I described above?

Thank you for your time in debugging the issue.

Comment 4

[James]

My thanks to everyone who worked on this.  I just downloaded the current version (60.0.2) and was NOT able to recreate the problem.  Google Maps now works as expected!

Comment 5

[Timea Cernea [:tbabos][inactive]]

Some good news right there! 
Based on Comment 4, I'm closing this issue as Resolved - WFM.
If anyone can still reproduce it, please re-open the issue and provide further information.

Comment 6

[giga.camp0s]

Same problem here (and I'm not alone among my colleagues): we go on google maps, search an address and after few seconds (under a minute) the tab does not respond anymore to the mouse. I need to double check if it happens just by navigating on the map without the "search" part.

The other tabs are still working (just web pages) AND if I got back to the g.maps tab I see a light brown background and a spinning symbol in the middle. The map does not come back.

Sometimes I can still close the tab with the "x" on the tab label; otherwise I need the task manager to kill all the firefox.exe beacuse the close button on the whole Firefox windows does nothing too.

If it was possible to close the tab, it is still possible to open a new tab and paste the previous address of the map, at this point it will hang again 90% - the remaining 10% of the times it will finally work without hanging.

We have in common a "Dell Latitude E6530" and windows 7 64b. As I can remember it started shortly before the 60.x version.

I can reproduce this behaviour always, let me know what I should record or run alongside Firefox, in order for anybody to capture a trace that you can analyze.

Comment 7

[Timea Cernea [:tbabos][inactive]]

Hi giga.camp0s,

I would also like to know if the issue is reproducible in the same way using a clean Firefox profile and also Safe Mode (link for them in Comment 1). It would be highly important to know in order to bring up the issue to the development team.
Might also be good to check if it reproduces on the latest Nightly version.

Thank you.

Comment 8

[James]

The issue appears to be resolved and all that I did was to uninstall Firefox and then install the Nightly Build version (62.0b3 - 64bit) from the beta update channel.  The problem persists if I use the standard version.

Comment 9

[Timea Cernea [:tbabos][inactive]]

Just to clear things up since looks like we messed up a bit the latest Firefox versions:

Firefox Nightly 62.0a1 (nightly update channel) - download link here: https://archive.mozilla.org/pub/firefox/nightly/2018/06/2018-06-26-22-01-24-mozilla-central/
Firefox Beta 62.0b3 (beta update channel) - download link here: https://archive.mozilla.org/pub/firefox/candidates/62.0b3-candidates/build1/
Firefox Release 61.0 - "standard" (release update channel) - download link here: https://archive.mozilla.org/pub/firefox/releases/61.0/

Can you please re-check on which Firefox version is the issue reproducible on? Based on Comment 4, it was not reproducible anymore after the update for Firefox Release.

In Comment 8 you mention that the problem is still reproducible on Release version(standard). Also, based on the same comment I understand that the issue does not occur on latest Nightly version. However "62.0b3 from the beta update channel" goes with Firefox Beta version. I am really confused right here.

So, as I mentioned earlier, please re-test the issue using clean firefox profile and report back mentioning the corresponding Firefox versions for each test result. I understand that Firefox builds are often updated during development and might cause confusion regarding it's versions so please ask if you encounter any misunderstandings. It is highly important to track down which FF version has this issue in order to help the development team to fix it. Will re-open the issue for now. 

Thank you.

Comment 10

[James]

Attachment: screenshot of Firefox version

Comment 11

[James]

My apologies for not being clear about the Firefox version that I am running.  I have attached a screenshot of the "About Firefox" window to show you exactly what I am running.

Also -- Firefox Support (you folks) have been excellent.  I shall carry out your instructions later today and get back to you with the results...

Comment 12

[Timea Cernea [:tbabos][inactive]]

That's indeed newly released Firefox Beta! Looking forward for your results for all the remaining 2 Firefox version (Nightly, Release)
So far we know that it does not occur on Beta (62.0b3).

Comment 13

[giga.camp0s]

So just to follow up, with the update to 61.0.. it works again as intended! no more freezes, google maps is smooth and responsive as before 59.x.

Comment 14

[James]

To clarify, the current standard build still have the problem.  I am currently in the beta channel using version 62.0b7 and the problem with Google Maps is not present (Google Maps works fine).

Comment 15

[get_logan]

I get intermittent freezes in google maps if I install the CanvasBlocker extension.

Affects Firefox stable 61.0.1, beta 62.0b7 and latest nightly 63.0a1 (2018-07-10).

Does not seem to happen if I switch to "Satellite" view in google maps.

Here is a performance profile I recorded using a new profile in nightly 63.0a1 (2018-07-10) with only CanvasBlocker installed:
https://perfht.ml/2KLVRjE

Comment 16

[Timea Cernea [:tbabos][inactive]]

Thanks everyone for the feedback as well as performance profile!
I will assign a component to involve the development team to review this issue.

Comment 17

[Nicolas Silva [:nical]]

The profile doesn't show anything gfx related although there are big blocks of js execution.

Comment 18

[Kannan Vijayan [:djvj]]

see: https://perfht.ml/2REhrpQ

There are two big chunks of time being spent in the long blocking areas here.

The first is a huge amount of time (38%) in ProxySetPropertyByValue, and another large chunk (27%) in HTMLCanvasElement.toDataURL.

The former is just cross-compartment proxy nuttery, I asssume.

The latter seems to be a large chunk of blocking time being spent in PNG creation from a canvas element.

Comment 19

[Jan de Mooij [:jandem]]

Adding dependency per comment 18.