686157 - CPU spikes and multi-second lockups (switching tabs and typing)

Status: RESOLVED INCOMPLETE

(Firefox :: Session Restore, defect)

Description

[Ryan Jones-Ward [:sciguyryan]]

Attachment: CPU Spikes

This isn't a new problem and I've had it for a while. I've set up a new profile several times and it always ends up returning exactly the same.

I have had no success tracking this down. I have disabled all addons, created new profiles (which start off working and then the same thing starts again) and altered every setting I can think of.

I've included a graph from Process Explorer showing the spikes. Each of those occurred while attempting to switch tabs or typing in a text box. Each of these results leads to a multi-second lockup that completely renders the browser unusable.

The value represents 12.5% CPU usage - the maximum possible for a single thread application on a quad core processor with hyper threading enabled.

Is there anything I can run to help pinpoint what is causing this? It happened a lot while filling this bug for example and has made the browser worthless for any decent use.

Comment 1

[(mostly gone) XtC4UaLL [:xtc4uall]]

Maybe a WinDbg Log can help?
https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg

Comment 2

[Ryan Jones-Ward [:sciguyryan]]

(In reply to XtC4UaLL [:xtc4uall] from comment #1)
> Maybe a WinDbg Log can help?
> https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg

I've never got that thing to work correctly on my system unfortunately.

However I had a bit of a breakthrough. This seems to being caused by session restore. After deleting the session file and re-opening exactly the same tabs it appears to have fixed the problem.

I've retained the session files in case anyone wants to take a look at them, if you do post here and I'll e-mail them over.

Comment 3

[Emanuel Hoogeveen [:ehoogeveen]]

Related to bug 669034 or bug 467409?

Comment 4

[Ryan Jones-Ward [:sciguyryan]]

(In reply to Emanuel Hoogeveen from comment #3)
> Related to bug 669034 or bug 467409?

Most likely related to bug 669034.

Comment 5

[Paul O'Shannessy [:zpao] (not bugmail, email directly)]

Ryan, if you still have your sessionstore.js, that would be helpful in figuring out which bug this can be duped to (there are a couple "Snappy" bugs that are related)

Comment 6

[Wayne Mery (:wsmwk)]

(In reply to Ryan Jones from comment #4)
> (In reply to Emanuel Hoogeveen from comment #3)
> > Related to bug 669034 or bug 467409?
> 
> Most likely related to bug 669034.

Ryan, dDo you still sessionstore.js file that has this problem?

Comment 7

[David Teller [:Yoric] - still alive but not very active]

By now, we have managed to remove most of the causes for Session Restore CPU spikes. We are working on the remaining ones.

Comment 8

[Ryan Jones-Ward [:sciguyryan]]

(In reply to Wayne Mery (:wsmwk) from comment #6)
> (In reply to Ryan Jones from comment #4)
> > (In reply to Emanuel Hoogeveen from comment #3)
> > > Related to bug 669034 or bug 467409?
> > 
> > Most likely related to bug 669034.
> 
> Ryan, dDo you still sessionstore.js file that has this problem?

Unfortunately I no longer have it. The original report was quite some time ago and my computer failed a month or so after the original report was raised. The session file wasn't something I had a backup of. I haven't noticed this repeat recently so the issue has likely been resolved.

Comment 9

[Wayne Mery (:wsmwk)]

Ryan, Thanks for the update.