On Mon, Jan 16, 2006 at 12:55:06AM -0500, Jason Dorje Short wrote:
> Eric Dorland wrote:
> >reassign 324791 firefox
> >thanks
> >
> >* Jason Dorje Short ([EMAIL PROTECTED]) wrote:
> >
> >>Package: mozilla-firefox
> >>Version: 1.0.6-3
> >>Severity: normal
> >>
> >>
> >>Firefox crashed (actually my power went out and the whole system went 
> >>down in
> >>an instant).  When I restarted it, it refused to use my default profile. 
> >>Naturally the lock file in ~/.mozilla/firefox/*.default/lock was still 
> >>there;
> >>removing this fixed the problem.  This lockfile pointed to 127.0.0.1:5371 
> >>but
> >>there was no such process running.  (After I removed the lock and 
> >>restarted,
> >>the new lock pointed to 5543; `ps -p 5543` showed that this was indeed
> >>firefox.)  I think I've seen this behavior before but I can't be certain.
> >>
> >>If I kill firefox manually (killall -SEGV firefox-bin) there is no 
> >>problem.
> >>Only if there's a computer restart does the problem show up (I haven't
> >>tried killing the process and then restarting the computer before bringing
> >>firefox back up; that might show the same symptoms).
> >
> >
> >I'm not sure what the bug is here. This is a common problem with lock
> >files. 
> 
> Common but both solvable and poorly handled.
> 
> The common solution is for the lock to include the PID of the locking 
> process, so that when acquiring the lock it's possible to check for 
> stale locks.
> 
> The problem is handled poorly because there is no way to fix it!  Unless 
> you go in and delete the lock file by hand, it will never go away.  The 
> typical user will then see the "Pick profile" screen every time they log 
> in and will be unable to return to their default profile.
What is the expected (desired?) behaviour?  Check the indicated PID,
and if it is not a firefox process, remove the lock automatically?
(Could be implemented on linux by checking /proc/$pid/exe symlink).

-- 
Clear skies,
Justin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to