Closed
Bug 105029
Opened 24 years ago
Closed 24 years ago
Cannot get New Navigator Window
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: juergen, Assigned: paulkchen)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.5) Gecko/20011011
BuildID: 2001101117
Occasionally it happens that I cannot get new browser windows from Mozilla.
I had about 10 Browser windows open and pressed ^N for a new one. The cursor
would shortly become a busy cursor and then go back to normal state. Else
nothing happens. Same selecting the menu entry.
When I closed all Mozilla windows (by repeating ^W), Taskmanager still showed a
95 MB Mozilla process.
Starting Mozilla from the start menu icon would do nothing.
Not until I killed that left-over process from Taskmanager could I get a new window.
This happend with 0.95 under NT4.0 SP 6, but formerly also with 0.94.
NT and Mozilla were up for two days.
I do not know how to reproduce that problem.
Reproducible: Couldn't Reproduce
Comment 1•24 years ago
|
||
Reporter:
This bug is difficult to fix because we can't reproduce it !
We have already a bug with this problem :
Try the URL in bug 104650 and you can't open a new browser window and mozilla
remeains in the memory after closing all windows
Comment 2•24 years ago
|
||
->Apps
Assignee: asa → pchen
Component: Browser-General → XP Apps
QA Contact: doronr → sairuh
Comment 3•24 years ago
|
||
WFM 2001101909 on Win2k.
Reporter: You may wish to try a fresh profile. You can manage/create profiles
with "mozilla.exe -profilemanager".
Comment 4•24 years ago
|
||
I can reproduce it at will, In fact I cannot get rid of it.
I cannot manage to find a way to open a new window and when I quit mozilla
it sticks around as a task that need to be killed.
I have tried a new profile and it made no difference.
This is on Windows NT 4.0 sp6a using 0.9.5(talkbalk) (and the latest build
03/11/01)
I was running 0.9.4 without any problems, I upgraded to 0.9.5 and I got
bug 104465 (aka: Entry point not found ?ToNewCString@nsString@@QBEPADXZ could
not be located in xpcom.dll)
I then upgraded to the latest build and got the same problem, rebooted then
mozilla would not start, I would get the splash then mozilla would just quit.
I then downgraded to 0.9.5, got bug 104465 again (once) and then got this
problem. (I do not get bug 104465 any more thought)
Is there any file or other info needed to track this one down?
Comment 5•24 years ago
|
||
jfp@clearfield.com:
Have you installed mozilla in a fresh directory (not over an older build) ?
If you got bug 104665, you have installed mozilla over an older/newer build.
(you should not do that)
Please uninstall mozilla, deleted all files that the uninstaller had not deleted
and reinstall mozilla. (backup your plugins directory first)
Comment 6•24 years ago
|
||
Uninstalling mozilla, deleting the \programs files\mozilla.org\mozilla directory
and reinstalling 0.9.5 did fix the problem, so I guess this behaviour
should be considered as a new mozilla over old problem.
Comment 7•24 years ago
|
||
okidoke!
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 8•24 years ago
|
||
mass verification of WorksForMe bugs: to find all bugspam pertaining to this,
set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM".
if you think this particular bug is *still* an open issue, please make sure of
the following before reopening:
a. that it's still a problem with ***recent trunk builds*** on the all
appropriate platform[s]
b. provide clear steps to reproduce (unless a good test case is already in the
bug report), making sure it pertains to the original problem (avoid morphing as
much as possible :)
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•