506876 - Fails to exit when profile is in NFS

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Nicos Gollan]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1) Gecko/20090718 Iceweasel/3.5.1 (Debian-3.5.1-1)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1) Gecko/20090718 Iceweasel/3.5.1 (Debian-3.5.1-1)

Firefox 3.5.1 still fails to exit with the profile in an NFS mount. It will fail to delete the "lock" or .parentlock files, and fails to close the SQLite databases most of the time.

Reproducible: Sometimes

Steps to Reproduce:
1. Exit Firefox
Actual Results:  
The profile is not closed properly.

Expected Results:  
Databases should be left without a journal and the lock files should be deleted.

"NFS is lying to us" as in #473624 is not an excuse. Even KDE can cope with the same NFS mount, and that's saying something.

Marking it as "major" since exiting an application should be pretty high on the feature list, especially considering bugs like #147659 that require frequent restarts.

Comment 1

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.12 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Also, please consider using the most recent Firefox 4 beta build, your bug may be resolved there.

Comment 2

[Nicos Gollan]

This bug is caused a conceptual weakness of SQLite, which depends on FS-level locking of the database files. The bug does not seem to occur when server-side locking is disabled on the client mounting the NFS export.

Somewhat related, I tried submitting a workaround for resulting locked database files (stale serverside locks) on the help website, which was turned down because it was "too technical".

FWIW, I consider this bug something like WONTFIX DONTCARE.

Comment 3

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.