1278587 - FF becomes unresponsive with AWS console opened in another tab/window

Status: RESOLVED INCOMPLETE

(Core :: JavaScript Engine: JIT, defect, P3)

Description

[Alex]

What did you do?
================
1. Opened several FF windows with different sites in different tabs
2. Open AWS Cloudwatch homepage console with several Alarm Summary charts in a tab


What happened?
==============
After some time FF becomes unresponsive for 20-40 seconds, then it comes back and works well until the next freezing (which happen in several minutes).
Logging out of AWS console stops issue from happening.

What should have happened?
==========================
FF shouldn't become unresponsive

Is there anything else we should know?
======================================
I have 3 FF windows with around 40 tabs in total. Working under Windows 7 Pro x64 RUS, Intel i3, 8GB RAM, 128GB SSD.

Comment 1

[Alex]

Addon: during the unresponsiveness, FF loads the CPU up to 25%.

Comment 2

[Alex]

Couple more things:
1. Restarting FF w/o addons does not help
2. FF version is 46.0.1

Comment 3

[Cosmin Muntean [:cmuntean], Ecosystem QA]

I don't have a AWS account in order to verify this issue. Do you have a test account that you can share with us so we can reproduce the issue?

However, can you please retest this using latest Firefox release and latest Nightly build (https://nightly.mozilla.org/) and report back the results? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings or add-ons as a possible cause (https://goo.gl/PNe90E).

Comment 4

[Alex]

How to run nightly build along with the regular version simultaneously?

Comment 5

[Alex]

I don't have a shareable AWS account, sorry.

Comment 6

[Cosmin Muntean [:cmuntean], Ecosystem QA]

Download the standard Nightly build from https://nightly.mozilla.org/. After the download is complete, you can extract the installer in a new folder. After that start Firefox release (the one installed), then go to the folder in which you have the Nightly extracted installer, you can place the "firefox.exe" shortcut on your desktop (set to Desktop). Go to desktop find the newly created shortcut, right click it, go to Properties and under the Shortcut tab, add "-p -no-remote" to the target. It should look something like: <<"C:\Program Files\Mozilla Firefox\firefox.exe" -p -no-remote>>. Click OK and start the browser from the shortcut.
A profile chooser dialog will appear and you can create a new profile without affecting the old one.

By starting the browser with a different profile you can have both instances of Firefox running.

Comment 7

[Alex]

The issue is repeatable with FF nightly build (50.0a1 (2016-06-15)). I'm running the clean profile but has logged into FF Sync to synchronize my passwords, bookmarks, history and preferences. No addons were installed.
Attaching the Windows TaskManager snippet which shows the current load.

Comment 8

[Alex]

Attachment: ff_load.png

Comment 9

[Alex]

It should be mentioned that there are only 2 FF windows: 8 tabs in the 1st and two tabs in the 2nd.

Troubleshooting information below:
Application Basics
------------------

Name: Firefox
Version: 50.0a1
Build ID: 20160615030209
Update Channel: nightly
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
OS: Windows_NT 6.1
Multiprocess Windows: 2/2 (Enabled by default)
Safe Mode: false

Crash Reports for the Last 3 Days
---------------------------------

All Crash Reports

Extensions
----------

Name: Firefox Hello
Version: 1.4.0
Enabled: true
ID: [e-mail]

Name: FlyWeb
Version: 1.0.0
Enabled: true
ID: [e-mail]

Name: Multi-process staged rollout
Version: 1.0
Enabled: true
ID: [e-mail]

Name: Pocket
Version: 1.0.3b1
Enabled: true
ID: [e-mail]

Name: Web Compat
Version: 1.0
Enabled: true
ID: [e-mail]

Graphics
--------

Features
Compositing: Direct3D 11
Asynchronous Pan/Zoom: wheel input enabled; touch input enabled
WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Direct3D11 vs_4_1 ps_4_1)
Hardware H264 Decoding: Yes; Using D3D9 API
Direct2D: true
DirectWrite: true (6.2.9200.17568)
GPU #1
Active: Yes
Description: Intel(R) HD Graphics
Vendor ID: 0x8086
Device ID: 0x0102
Driver Version: 8.15.10.2696
Driver Date: 3-19-2012
Drivers: igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32
Subsys ID: 00000000
RAM: Unknown

Diagnostics
AzureCanvasAccelerated: 0
AzureCanvasBackend: direct2d 1.1
AzureContentBackend: direct2d 1.1
AzureFallbackCanvasBackend: cairo





Important Modified Preferences
------------------------------

accessibility.typeaheadfind.flashBar: 0
browser.cache.disk.capacity: 358400
browser.cache.disk.filesystem_reported: 1
browser.cache.disk.smart_size.first_run: false
browser.cache.disk.smart_size.use_old_max: false
browser.cache.frecency_experiment: 1
browser.download.importedFromSqlite: true
browser.places.smartBookmarksVersion: 8
browser.sessionstore.upgradeBackup.latestBuildID: 20160615030209
browser.startup.homepage: about:blank
browser.startup.homepage_override.buildID: 20160615030209
browser.startup.homepage_override.mstone: 50.0a1
browser.urlbar.maxRichResults: 12
dom.apps.lastUpdate.buildID: 20160615030209
dom.apps.lastUpdate.mstone: 50.0a1
dom.apps.reset-permissions: true
dom.push.userAgentID: abfb2a8210954908bd1a1ed440060aab
extensions.lastAppVersion: 50.0a1
media.gmp-eme-adobe.abi: x86-msvc-x64
media.gmp-eme-adobe.lastUpdate: 1466072176
media.gmp-eme-adobe.version: 17
media.gmp-gmpopenh264.abi: x86-msvc-x64
media.gmp-gmpopenh264.lastUpdate: 1466072177
media.gmp-gmpopenh264.version: 1.5.3
media.gmp-manager.buildID: 20160615030209
media.gmp-manager.lastCheck: 1466072174
media.gmp-widevinecdm.abi: x86-msvc-x64
media.gmp-widevinecdm.lastUpdate: 1466072179
media.gmp-widevinecdm.version: 1.4.8.866
media.gmp.storage.version.observed: 1
media.hardware-video-decoding.failed: false
network.cookie.prefsMigrated: true
network.predictor.cleaned-up: true
places.database.lastMaintenance: 1466077441
places.history.expiration.transient_current_max_pages: 104858
plugin.disable_full_page_plugin_for_types: application/pdf
plugin.importedState: true
privacy.donottrackheader.enabled: true
security.disable_button.openCertManager: false
security.OCSP.enabled: 0
security.sandbox.content.tempDirSuffix: {9857540a-da51-453b-bc2a-ad7c955379e6}
services.sync.declinedEngines: tabs
services.sync.engine.addons: false
services.sync.engine.prefs.modified: false
services.sync.engine.tabs: false
services.sync.lastPing: 1466072250
services.sync.lastSync: Thu Jun 16 2016 18:20:49 GMT+0300
services.sync.numClients: 3
storage.vacuum.last.index: 0
storage.vacuum.last.places.sqlite: 1466077441

Important Locked Preferences
----------------------------

Places Database
---------------

JavaScript
----------

Incremental GC: true

Accessibility
-------------

Activated: false
Prevent Accessibility: 0

Library Versions
----------------

NSPR
Expected minimum version: 4.12
Version in use: 4.12

NSS
Expected minimum version: 3.25
Version in use: 3.25

NSSSMIME
Expected minimum version: 3.25
Version in use: 3.25

NSSSSL
Expected minimum version: 3.25
Version in use: 3.25

NSSUTIL
Expected minimum version: 3.25
Version in use: 3.25

Experimental Features
---------------------

Comment 10

[Ryan VanderMeulen [:RyanVM]]

Hi Alex, thanks for hanging in there with this report. Unfortunately, problems like these are difficult to diagnose and debug, especially when the site requires authorization. Would you be willing to try collecting a profile of the hangs to see if anything stands out there? The link below has directions for how to collect and submit a profile.
https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler

Thanks!

Comment 11

[Alex]

Hi Ryan. After clicking "analyze" in gecko plugin, i get an error (check the screenshot). Please, advise.

Comment 12

[Alex]

Attachment: ff_debug.png

Comment 13

[Cosmin Muntean [:cmuntean], Ecosystem QA]

Hi Alex, 

I got the same error, but after pressing "ok" button the page is successfully loaded and you can generate a link that you can share it with us. Can you please try again?

Comment 14

[Alex]

https://cleopatra.io/#report=ffa379cf8e7b37bcb92f7ab25df7e4fe4cc4dc96

Comment 15

[Cosmin Muntean [:cmuntean], Ecosystem QA]

Hi Alex, 

It seems I did not pay close attention to your screenshot from comment 12. The error that you were receiving actually made the profile that you generated unusable because it was an error with "symbolication" and instead of getting function names we got random numbers and characters.

As the "Symbolication Filed" error is gone, can you please try again to collect a profile of the hang?

Comment 16

[Alex]

Took some time..
https://cleopatra.io/#report=8305d89380a8bcb19341c425f1b10fa2dc87465d

Comment 17

[Terrence Cole [:terrence]]

About 99% of the samples with the (AWS console open) are in jit code, which means that the site is spinning constantly. This might be because the site is just buggy, or it might be because we're hitting a fantastically slow path and failing to run fast enough to keep up. Someone from SpiderMonkey should take a closer look.

Comment 18

[Justin Wood (:Callek)]

Got pinged on IRC to see if I can help reproduce, (I'm not primarily using windows now, but still have it handy enough that I can try by next week)

Comment 19

[Alex]

OK. JFYI: Google Chrome doesn't have this issue.

Comment 21

[alex_mayorga]

¡Hola!

Marking NEW as there's at least a duplicate at https://bugzilla.mozilla.org/show_bug.cgi?id=1301460

¡Gracias!
Alex

Comment 22

[Francois Guerraz]

https://cleopatra.io/#report=e02280b6c4cd4df322e5e54d5739a7c3e2b1deeb

Complete lock up for a few seconds.

Comment 23

[Francois Guerraz]

It's interesting to note that I don't seem to be able to reproduce the bug when the profiler is enabled. In the profile I've just sent, I have enable profiling /during/ the lockup.

Comment 24

[Alex]

Hi Matthew. It's nice you nailed down the 7-years old bug! Could you share some details on what's caused it? A link to the fixing commit would be also nice to have! Thanks!

Comment 25

[Matthew Gaudet (he/him) [:mgaudet]]

Note: this was resolved as Incomplete, not Fixed. We've not had much activity on this bug for 7 years -- which means that an appreciable fraction of both the AWS and Firefox codebases will have changed.

If you still see this, would be great to have this reopened with more details, but by closing as incomplete we remove this from the backlog of bugs.