Closed
Bug 301529
Opened 19 years ago
Closed 19 years ago
Sometimes fail to reclaim a profile lock on Linux
Categories
(Core Graveyard :: Profile: BackEnd, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 151188
People
(Reporter: roc, Assigned: roc)
Details
It's possible a user to reboot their machine and then discover that Firefox
won't start because their profile appears to be locked. This can happen when the
PID in the lockfile gets assigned to a process on startup, so that Firefox sees
there is process alive and assume's it's holding the lock. This is really bad.
We need a way to detect whether the process is really a Firefox instance,
preferably the Firefox instance that obtained the lock in the first place.
Comment 1•19 years ago
|
||
yup
*** This bug has been marked as a duplicate of 151188 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•