Closed
Bug 1486715
Opened 6 years ago
Closed 6 years ago
Firefox consumes 100% CPU and freezes when opening a window (since Quantum)
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: colas.doute, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180807170231
Steps to reproduce:
I work on an application that manages to open some pages in windowed mod (not tabs). Since Quantum, when we open thoses pages, there is a problem described as follow. The problem was reproduced in Firefox 57, 58, 59 and 60.0.1
Actual results:
The window opens and then freezes during the loading. CPU goes to 100% and stays at 100% until you close the window. Firefox doesn't crash.
The problem doesn't occurs on tabs : If i change the window.open function to make it a tab, there is no problem. But if i grab the tab to make it a window and then reloads the page, the problem occurs.
Expected results:
The page should load correctly.
The things i found : The company i work for uses an SSO that automatically fills logins/passwords for internal applications. It uses Accessibility to work on Firefox. If we disable the SSO, the problem is fixed. If we disable accessibility function, the problem is fixed.
Those cannot be definitive solutions as they are used for other applications.
I also know that disabling graphic acceleration fixes the problem.
I'm not an expert in debugging Firefox so tell me if you need more informations relative to the problem.
Comment 1•6 years ago
|
||
Jamie, either this is another case where that SSO crawls the entire accessibility tree in a very slow manner to get to the password field, or we have a problem that specifically affects windowed mode. Thoughts?
Flags: needinfo?(jteh)
Comment 2•6 years ago
|
||
For debugging, it would be helpful to get access to a sample application that exhibits this problem. Also, it is worth trying with Firefox 63 Nightly just to see if the problem has been fixed. There were a lot of changes between 60 and 63.
Flags: needinfo?(colas.doute)
Reporter | ||
Comment 3•6 years ago
|
||
Unfortunately i can't try Firefox 63 right now cause it should first be validated/parametrized by the company before making it available for use on their computer. I'll try to test it as soon as i can
For the sample, the SSO requires a license and the application itself can't be published. I may try on my spare time to build a specific example to give you.
About the first comment, the pages impacted doesn't have fields with login/password. Don't know if that helps.
Flags: needinfo?(colas.doute)
Comment 4•6 years ago
|
||
Unfortunately, there probably isn't much we can do here without access to the SSO in question. Can you provide details of the SSO software being used? Perhaps we can establish contact with the vendor. The symptoms do suggest that the SSO is crawling the accessibility tree in a very inefficient manner.
Does this happen if you drag *any* tab into a new window or only tabs from this specific web application?
We *may* be able to gather some information from a performance profile, though I'm not hopeful this will be enough. If you want to try this, see this page for details about how to collect one:
https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem
Flags: needinfo?(jteh)
Comment 5•6 years ago
|
||
Resolving incomplete since there hasn't been any activity in nearly a year and we don't have sufficient information/test cases to make this actionable.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•