Closed
Bug 177
Opened 26 years ago
Closed 26 years ago
Running NavCenter when another browser has lock gives asserts
Categories
(MozillaClassic Graveyard :: XFE, defect, P2)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: mcguirk, Assigned: slamm)
Details
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•26 years ago
|
Assignee: nobody → slamm
Component: XFE
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•26 years ago
|
||
Marking Assigned.
Comment 2•26 years ago
|
||
Is this bug still valid in the new world? If not, please mark resolved, won't fix. Thanks.
Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
Assignee | ||
Comment 4•26 years ago
|
||
This bug does not apply in the new world. Marking invalid.
You need to log in
before you can comment on or make changes to this bug.
Description
•