system was running with high cpu usage as I was doing other things, whilst using firefox

Bug #89267 reported by Sam Cater on 2007-03-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Mozilla Bugs

Bug Description

Binary package hint: firefox

system was running with high cpu usage as I was doing other things, whilst using firefox

heres the bug report

Thank you Sam for this bug report.

Retrace done. Seems to be the known gtk theme issue that should be fixed soon in edgy as already is in feisty.

Marking as dup

Changed in firefox:
assignee: nobody → mozilla-bugs
status: Unconfirmed → Needs Info

This response was for bug 89379 (need to do a proper retrace for this bug) Assigned to me.

Changed in firefox:
assignee: mozilla-bugs → hmontoliu

Cannot get a better retrace. Assigned to gnomefreak to see if he can get a better one.

Changed in firefox:
assignee: hmontoliu → gnomefreak
John Vivirito (gnomefreak) wrote :

Can you please provide us with step by step instructions on what you were doing when it crashed so we can try to reproduce this bug, also what extentions, addons, or themes do you have installed?

John Vivirito (gnomefreak) wrote :

Finished retrace. uploaded stack and thread*
Assigning this to alexander for review and summary.

Changed in firefox:
assignee: gnomefreak → asac
Alexander Sack (asac) wrote :

not a good stacktrace. Cannot create a summary from that. Thus, rejecting. If you ever get a new crash, feel free to open a NEW report.

Sorry and thanks,


Changed in firefox:
assignee: asac → mozilla-bugs
status: Needs Info → Rejected

Sam Cater, thank you for reporting this and helping make Ubuntu better. Edgy reached EOL on April 26, 2008.
See this document for currently supported Ubuntu releases: .

As well, your crash report is manually attached. If this is reproducible in a supported release, please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:

Changed in firefox (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers