1372090 - Firefox process spinning on CPU

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[vhaisman]

Attachment: firefox-spinning.csv

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170518000419

Steps to reproduce:

I leave my PC on and every morning, I come to mostly unresponsive Firefox and one of its sub-processes is spinning.

I have attached a stack trace as captured by System Internals' Process Monitor.


Actual results:

Firefox spinning on CPU and being unresponsive.


Expected results:

Firefox not spinning on CPU and being responsive. Duh!

Comment 1

[Simona Badau, Desktop QA]

Vhaisman, 

Could you please try to do the following?
1. Update to the latest Firefox 54.
2. Run Firefox in Safe mode and see if you encounter the same behavior.

You can find more details about the above requests along with some new troubleshooting methods, here:
https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix

Please let us know the results.

Thank you!

Comment 2

[vhaisman]

The CPU spinning happens also with version 54.0.

After setting up Mozilla symbol server, I have been able to capture the following call stack on the offending thread:

ntoskrnl.exe!KiSwapContext+0x7a
ntoskrnl.exe!KiCommitThreadWait+0x1d2
ntoskrnl.exe!KeWaitForSingleObject+0x19f
ntoskrnl.exe!KiSuspendThread+0x54
ntoskrnl.exe!KiDeliverApc+0x21d
ntoskrnl.exe!KiApcInterrupt+0xd7
xul.dll!js::UncheckedUnwrap+0x32
xul.dll!mozilla::dom::CallbackObject::operator==+0x2e
xul.dll!mozilla::EventListenerManager::AddEventListenerInternal+0x576
xul.dll!mozilla::EventListenerManager::AddEventListenerByType+0x75
xul.dll!mozilla::EventListenerManager::AddEventListener+0x82
xul.dll!mozilla::EventListenerManager::AddEventListener+0x46
xul.dll!nsGlobalWindow::AddEventListener+0x77
xul.dll!mozilla::dom::EventTargetBinding::addEventListener+0x1c7
xul.dll!mozilla::dom::EventTargetBinding::genericMethod+0x13f

Comment 3

[ovidiu boca[:Ovidiu]]

Hi Vhaisman,

Can you please capture a gecko profile using the steps from here: https://luke-chang.github.io/autofill-demo/basic.html, thanks. 
This way maybe we can figure out what causes this issue.

Comment 4

[vhaisman]

(In reply to ovidiu boca[:Ovidiu] from comment #3)
> (...)

FYI, this is a phishing spam link.

Comment 5

[ovidiu boca[:Ovidiu]]

Vhaisman, you are saying that you can't capture a gecko profile?

Comment 6

[vhaisman]

(In reply to ovidiu boca[:Ovidiu] from comment #5)
> Vhaisman, you are saying that you can't capture a gecko profile?

I am saying the link you have provided in #3 is **** link.

Comment 7

[ovidiu boca[:Ovidiu]]

Sorry for that, here is the correct link https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem   , here you can find the steps in order to obtain a gecko profile.

Comment 8

[ovidiu boca[:Ovidiu]]

Based on the fact that Vhaisman didn't obtain a profile, I will close this as resolved Incomplete. Vhaisman please fell free to reopen this issue if you can reproduce this or you obtained a gecko profile. Thanks