Closed Bug 713544 Opened 9 years ago Closed 3 years ago uses excessive CPU and freezes Firefox when there is a lot of history


(Toolkit :: Places, defect)

8 Branch
Not set





(Reporter: isaaclw, Unassigned)


User Agent: Mozilla/5.0 (Ubuntu; X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0
Build ID: 20111115183813

Steps to reproduce:

I enabled safe-mode browsing with Firefox, and then played a game of dominion at

Actual results:

As soon as the JavaScript started doing it's work, Firefox maxed out a core. The game was able to (for the most part) keep up, however it occasionally crashes, forcing me to re-load firefox.

Expected results:

It should have used a more reasonable amount of CPU.
> it occasionally crashes

Please submit the crash data and then after it restarts load about:crashes
in the URL bar and provide a few crash IDs from the list.  Thanks.
Component: General → Untriaged
QA Contact: general → untriaged
I'm afraid I may have used the wrong word (and I should have known better).
Instead of saying "crash", I should have said "freezes". I imagine my "about:crashes" contains data about how I force closed it. I'll still attempt to load it.

Also, I noticed on a clean installation of firefox (on another computer) this address had no issues. I'll attempt to replicate my issue in a virtual environment so that I can better understand what's causing it.
Component: Untriaged → General
Alright, so I cleared out a few things, but the only thing of any significance was my history .
That seemed to have done the trick.

One thing I'd like to know is WHY my excessive history affected, and no other sites...
Component: General → History: Global
Product: Firefox → Core
QA Contact: untriaged →
Summary: uses excessive CPU and crashes firefox → uses excessive CPU and freezes Firefox when there is a lot of history
Good question.  Marco, any ideas?
Component: History: Global → Places
Product: Core → Toolkit
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.