1427979 - Page becomes unresponsive at random times

Status: RESOLVED WORKSFORME

(Firefox :: Untriaged, defect)

Description

[Kaartic Sivaraam]

This has been occuring randomly for some time now. Unfortunately, due to the randomness, I can't give specific Steps to reproduce this. The issue is essentially that described in bug 691830 except that I'm seeing it occur for variety of pages (it occured on that page too!). It's occuring too often recently.

The only thing that's notable is that I have a lot of tabs open in a lot of windows. That's because I use the "Show my windows and tabs from last time" for the "When Nightly starts" preference.

I've tried refreshing the page with suspicious add-ons disabled and it had no effect. I had to re-open that page in a new tab (sometimes in a new window) to bring back the responsiveness.

Environment details:
Version: 59.0a1 (2018-01-03) (64-bit)
OS: Debian GNU/Linux 9 (stretch)

Add-ons installed:
1. Those I've tried disabling:
   a. NoScipt
   b. HTTPS Everywhere
   c. Privacy Badger
2. Those I didn't try disabling:
   a. Test Pilot
   b. SnoozeTabs

Comment 1

[Ciprian Muresan [:cmuresan], Ecosystem QA]

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

Hi Kaartic,

I haven't been able to reproduce the issue you are experiencing on Firefox Release 54.0.4 and Nightly 59. In order to debug this further you should install the Gecko Profiler add-on found here: https://perf-html.io/, wait for the issue to manifest, start collecting data using the add-on and post the resulting profile here.

You can find more information about the add-on and how to use it here: https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler.

Comment 2

[Kaartic Sivaraam]

> wait
> for the issue to manifest, start collecting data using the add-on and post
> the resulting profile here.
>

Sure. It hasn't been manifesting recently. May be it was a heisenbug ;)

Comment 3

[Ciprian Muresan [:cmuresan], Ecosystem QA]

Based on comment 2 from the reporter and the fact that I can't reproduce the issue, changing status to RESOLVED-WORKSFORME.
If anyone can still reproduce it on latest versions, feel free to reopen the issue and provide more information.