Running NavCenter when another browser has lock gives asserts

VERIFIED INVALID

Status

MozillaClassic
P2
minor
VERIFIED INVALID
20 years ago
19 years ago

People

(Reporter: Dan McGuirk, Assigned: Steve Lamm)

Tracking

1998-03-31
x86
Linux

Details

(Reporter)

Description

20 years ago
Created by Dan McGuirk (mcguirk@indirect.com) on Monday, April 13, 1998 3:43:34 AM PDT
Additional Details :
If you run the NavCenter when another browser has the lock,
you get a lot of asserts from nlcstore.c (line 262 mostly,
and 294, and possibly one other.)

Maybe this is not really a bug, but shouldn''t asserts only
fail on things that should never, ever happen, not normal
error conditions?
Updated by Steve Lamm (slamm@netscape.com) on Thursday, April 30, 1998 10:45:00 AM PDT
Additional Details :
We need to add some logic that only allows you to run one Browser at a time, or
that makes the addition Browsers read-only.

If you do need to run two at once, you can create a second home directory.  I
usually test in a extra home directory.  For instance,

setenv HOME /u/slamm/.testhome

For starters, we could modify the code that pops up the lock dialog to popup a
dialog explaining the situation and then quiting.  We should probably allow
people to force the lock to go away too.

Updated

20 years ago
Assignee: nobody → slamm
Component: XFE
(Assignee)

Updated

20 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 1

20 years ago
Marking Assigned.

Comment 2

19 years ago
Is this bug still valid in the new world? If not, please mark resolved, won't
fix. Thanks.

Comment 3

19 years ago
Steve, is this a valid bug?
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID
(Assignee)

Comment 4

19 years ago
This bug does not apply in the new world.
Marking invalid.

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 5

19 years ago
Marking Verified.
You need to log in before you can comment on or make changes to this bug.