Firefox Slow and/or Causing High CPU Usage


One of the most likely cause of high CPU usage by Firefox is fragmentation of its database files (.sqlite files). If you have a habit of bookmarking and deleting unused bookmarks, places.sqlite, where bookmarks are stored, would be fragmented. You can shrink this file using sqlite3.

If you are using Windows OS, downlod this file from http://www.sqlite.org/download.html and extract the executable to C:\Windows folder (or any other folder included in the PATH variable).

If you are using Ubuntu, install sqlite3 using the following command
sudo apt-get install sqlite3

To shrink the database file, run the following command after replacing <your profile>  with your profile name

Windows:
sqlite3 "%APPDATA%\Mozilla\Firefox\Profiles\<your profile>\places.sqlite" "vacuum"

Ubuntu:
sqlite3 $HOME/.mozilla/firefox/<your profile>/places.sqlite "vacuum"

It is recommended that you take a backup of the sqlite file you are about to shrink.

If you wish to shrink all sqlite files, cd to the profile directory and run this command:

Windows:
for %i in (*.sqlite) do @echo VACUUM; | sqlite3 %i

Ubuntu:
for i in *.sqlite; do echo "VACUUM;" | sqlite3 $i ; done

If shrinking the file doesn't solve the problem:
  1. Take a backup of places.sqlite
  2. Start Firefox and export all your bookmarks
  3. Stop Firefox
  4. Delete places.sqlite file
  5. Start Firefox and import your bookmarks

Comments

  1. AnonymousOctober 24, 2011 at 6:12 AM

    The applications nowadays are more memory intensive as they are not constrained by the prices of memory. Get RAM for cheap at Amazon Corsair XMS3 8 GB

    ReplyDelete

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are creat...
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,...
Read more