Restarting without exiting Mozilla first gives me error



19 years ago
14 years ago


(Reporter: bugzilla, Assigned: dougt)


Windows 98

Firefox Tracking Flags

(Not tracked)




19 years ago
If you on a Win32 machine chooses Start->Restart without first quiting Mozilla 
you'll get an error saying:
"NSPR:EventReciever can shutdown"

Comment 1

19 years ago
Man, I have no idea who would own this.  Doesn't obviously fit any component 
either.  I hate to just pass this off blindly but maybe someone else will have 
a better guess.
Assignee: joki → chofmann
Component: Event Handling → other
QA Contact: janc → leger

Comment 2

19 years ago
Confirmed with 2000-02-17-08-M14 nightly binary on Windows NT, twice.
Each time a dialog came up saying "NSPR:EventReceiver cannot respond to a
shutdown request", and after clicking on [End Task], the same dialog appeared
twice more; after pressing the third [End Task] button, the shutdown continued.

A third time, the dialog said "mozilla.exe cannot respond to a shutdown request"
and again it reappeared twice before the rest of the shutdown procedure 

It didn't matter whether the Windows exit was via Start>Shutdown>Restart... or
Start>Shut Down>Shut down... This will annoy anyone who does not regularly
close their browser before shutting down windows.

Most crash-on-exit bugs show up in "Browser-General"; moving this there
for better visibility to those who might have a clue.
Assignee: chofmann → cbegle
Component: other → Browser-General
QA Contact: leger → asadotzler

Comment 3

19 years ago
I think is a big issue...
Users could be loosing data
Severity: normal → major

Comment 4

19 years ago
I just tried this on NT, and it worked okay. (2000-02-21 debug build) Can 
someone on Win98 confirm that it's still a problem?

Comment 5

19 years ago
I just tested with the newest build and here's how to reproduce:
- Disconnect from the network.
- Start Mozilla
- Launch mail

Try to restart Windows.

I'll try otherways too...

Comment 6

19 years ago
Ok.. I think you just have to start Mail and the try to restart.
This will give you an error.
You dont have to be disconnected from the net.

- Start Mozilla
- Start Mail
- restart Windows

Comment 7

19 years ago
wtc, can you look at this?  do you know of this error?
Assignee: cbegle → wtc


19 years ago
Whiteboard: plevent is no longer part of NSPR. Please reassign to one of brendan,dougt,dp,travis,troy.

Comment 8

19 years ago
plevent is no longer part of NSPR.  Please reassign to 
its new owners (brendan,dougt,dp,travis,troy).
Assignee: wtc → cbegle
Whiteboard: plevent is no longer part of NSPR. Please reassign to one of brendan,dougt,dp,travis,troy.

Comment 9

19 years ago
okay; updating owner to dougt; if it's not you, i guess you can try the next 
person down the line :)
Assignee: cbegle → dougt

Comment 10

19 years ago
setting milestone.
Target Milestone: M16

Comment 11

19 years ago
this may have been fixed by 33928.  I will try to verify this tomorrow.

Comment 12

19 years ago
I could not reproduce by either restarting or by sending a WM_CLOSE message to 
all windows in the process.
Last Resolved: 19 years ago
Resolution: --- → FIXED

Comment 13

19 years ago
Doesn't work in build 2000042512 on Win2000.
Open Mozilla
choose Start -> Shutdown -> Restart

Gives me the "ending process" dialog...
Resolution: FIXED → ---

Comment 14

19 years ago
not going to have time to fix for m16.  m17 bound.
Target Milestone: M16 → M17

Comment 15

19 years ago
moving out milestones.
Target Milestone: M17 → M26

Comment 16

19 years ago
Unable to reproduce this on Win2000 anymore....

Comment 17

19 years ago
has this problem gone away?  marking as worksforme.  QA can you verify on win98,
nt, and 2000?
Last Resolved: 19 years ago19 years ago
Resolution: --- → WORKSFORME
**Mass Spamm**
adding verifyme keyword to all worksforme bugs.
Keywords: verifyme
WFM (win98 92711). I actually restarted my computer testing it, worked just
fine. Verifying.

Comment 20

18 years ago
removing verifyme keyword.
Keywords: verifyme
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.