Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Why does the navigation bar hang when I type anything or click the arrow to view recent pages?

  • 3 replies
  • 3 have this problem
  • 2 views
  • Last reply by jstrunk

more options

Since Firefox 4, we have been unable to use the feature where the navigation bar searches your history and bookmarks as you type. It also no longer shows any items from the history when you click the down arrow.

This is only a problem on OS X with an NFS home directory. The navigation bar works with Firefox versions 3.6.12 through 3.6.18 at least. There may be earlier versions that work, but nothing since 4.0 has worked.

Turning off NFS locking is not an option for us.

Are there any settings to make Firefox more compatible with NFS home directories?

Since Firefox 4, we have been unable to use the feature where the navigation bar searches your history and bookmarks as you type. It also no longer shows any items from the history when you click the down arrow. This is only a problem on OS X with an NFS home directory. The navigation bar works with Firefox versions 3.6.12 through 3.6.18 at least. There may be earlier versions that work, but nothing since 4.0 has worked. Turning off NFS locking is not an option for us. Are there any settings to make Firefox more compatible with NFS home directories?

All Replies (3)

more options

A possible cause is a problem with the file places.sqlite that stores the bookmarks and the history.

more options

This is still an issue with Firefox 8.0.1 on all versions of OSX 10.5, 10.6, and 10.7 when using NFSv3, NFSv4, and AFP home directories. This has been an issue for all versions of Firefox >= 4. For some reason, the Awesome bar works in the latest versions of the Firefox 3 series. We don't want to rely on that because we don't know when you will stop updating it.

more options

I believe it is a places.sqlite issue, but none of the solutions on the linked page helped.