Closed
Bug 108416
Opened 24 years ago
Closed 24 years ago
mozilla process won't kill
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: wtopp, Assigned: asa)
Details
occasionally i find that when i "doubleclick" the mozilla icon i get the splash
panel, but then it just freezes there. that always means that mozilla.exe is
still active as a process even though the previous session had been shut down in
the windows way and all trace of active screens vanished. to the best of my
knowledge i am not running turbo mode, i have deselected it. this is mozilla
.9.4 btw, .9.5 broke some important forms and i can't use it.
the frozen splash results in a second mozilla.exe process shown in task manager.
the big problem is that one or both of the mozilla.exe processes that are now
active cannot be killed with task manager. i must reboot the computer to get
rid of them. task manager is showing no cpu usage, but the process is still
there and won't die and won't allow another mozilla session to start up. i am
rebooting almost every day because of this problem.
i am running win nt4 sp6a on a dual pentium ii box. there is just a chance this
is somehow an nt4 smp problem caused by the second processor, but i doubt it.
this may be a clue: netscape 4.7 occasionally does the same thing, no other app
anywhere on the box EVER does this.
Comment 1•24 years ago
|
||
Reporter, please try a nightly build to verify if the problem still exists or
wait for 0.9.6 to come out and see if you can reproduce the issue. Meanwhile I
am afraid you are using an outdated version of mozilla and your bugreport is of
no real use, sorry. ---> INVALID
I have had success in getting rid of rampant processes that task manager just
would not shut down with the "kill" utility from the NT resource kit. It is a
commandline tool that works just like the unix kill. Just say "kill <process
id>" on the console and mozilla should disappear. You can get the process id
from task manager. Good luck.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Comment 3•24 years ago
|
||
Diego: correct resolution would be WorksForMe
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → WORKSFORME
Comment 4•24 years ago
|
||
sorry for that SPAM
we don't accept bug reports from old builds.
0.9.5 is also too old but we accept it so long as we release our next milestone.
Can you try this:
Have you installed mozilla 0.9.4 in a fresh direcotry (no over another build ?)
You can try this: run "mozilla -profilemanager" and create a new profile.
That should fix your problem
bugzilla@uxp.de: correct resolution is invalid !
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 5•24 years ago
|
||
invalid
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → INVALID
Comment 7•24 years ago
|
||
And now a special edition of "Bugzilla - Bug Resolution Definition" for Matti
and Diego :
RESOLVED INVALID : The problem described is not a bug
RESOLVED WORKSFORME : All attempts at reproducing this bug were futile,
reading the code produces no clues as to why this behavior would occur.
And now :
[x] This is a bug
[ ] This is not a bug
[x] All attempts to reproduce this bug were futile
No - No, I won't reopen this bug. We'll meet again =)
Comment 8•24 years ago
|
||
Nobody meant to insult you, Markus. I still think it should be invalid. We can
continue this matter in private.
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•