Closed Bug 247827 Opened 20 years ago Closed 15 years ago

XPCOM Event Receiver stops OS shutting down by not closing

Categories

(Firefox :: Shell Integration, defect)

Product:
Firefox
Component:
Shell Integration
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: bugzilla, Unassigned)

References

Details

Attachments

(1 file)

Handle.exe output
3.08 KB, text/plain
Details 
User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040614 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040614 Firefox/0.8

Whenever I try to close down my Windows 98SE machine, after running Firefox 0.9
(and therefore, XPCOM Event Receiver) the OS comes up with a box saying 'Do you
want to close this program etc.' I click yes...nothing happens.
I try to close down my computer again, and the same thing happens.
I have sat there for about 1/2 an hour trying repeatedly to close down, and now
I just immediately resort to the mains switch.

Reproducible: Always
Steps to Reproduce:
1. Bootup Windows 98SE (I don't know about other OSs)
2. Start Firefox and do a little browsing - let XPCOM Event Receiver get warmed up
3. Close Firefox, and try to shut down.
4. Try to shut down again.
5. And again.
6. Yet again.
7. You can see where this is going, can't you?!

Actual Results:  
Went round in a loop, so I pulled the mains plug in frustration.

Expected Results:  
Closed, and let the computer shut down.

xpcom.dll

Build Config:
about:buildconfig

Build platform
target
i586-pc-msvc

Build tools
Compiler 	Version 	Compiler flags
$(CYGWIN_WRAPPER) cl 	12.00.8804 	-TC -nologo -W3 -nologo -Gy -Fd$(PDBFILE)
$(CYGWIN_WRAPPER) cl 	12.00.8804 	-TP -nologo -W3 -nologo -Gy -Fd$(PDBFILE)

Configure arguments
--disable-ldap --disable-mailnews
--enable-extensions=cookie,xml-rpc,xmlextras,pref,transformiix,universalchardet,typeaheadfind,webservices,inspector,gnomevfs,negotiateauth
--enable-crypto --disable-composer --enable-single-profile
--disable-profilesharing --enable-optimize --disable-debug --enable-codesighs
--disable-tests --enable-static --disable-shared --enable-official-branding
I am a computer literate, electronics engineer by trade.
I have just done a NEW FROM ORIGINAL CD of Windows 98SE and loaded several other
 general porpose programs AND have just loaded Mozilla Ver 1.7, got the same
error as disscussed by the originator, so uninstalled it, loaded Mozilla Ver
1.7.1, same again, uninstalled it, finally loaded FIREFOX Ver 0.9.2 and still
got the same error mentioned. This fault is repeatable (everytime).
I will add, this is more than an annoyance as data, usually setup type data, can
be lost, not to mention the added reboot time as Scandisk/Nortons reminds me to
"Please Shut the Computer Down Correctly in future", and 95% of the time my
bootup to shutdown time involces access to the internet.
If I can be of any assistance to this bug/(project) please do not hesitate to
contact me.

Regards, and keep up the good work!
XPCOM:EventRcvr hangs on for my Win2K as well.
Good news.
I have resolved my problem very simply.
My graphis card is a "ASUS V7700 Deluxe TV".
I had THE latest version driver installed named "nv5655_98SEME".
I simply reverted back to the original driver supplied on the CD that came with
the Video Card.
This fixed the problem.
(For the record I also tried the Video driver version prior to THE latest and
the fault was still present)

Moral - "The latest isn't always the best!"
In Windows XP, the Event Receoiver also hangs my computer. I'm using Firefox
1.0.3 with Profiles Manager enabled.
I see this consistently in WinXP SP2.  I use a .PAC proxy auto-config file, on a
Dell Latitute D600 laptop with an ATI Radeon 9000 Mobility video chipset (not
sure if that matters, or not).

This is a real pain, because each time I close and open Firefox, a firefox.exe
process remains running in the background, so by the end of the day I can have
quite a few of these ghost processes running.  I also noticed that it only seems
to happen when Firefox needs to write something to disk, whether it is saving a
preference or saving a cookie.
Flags: blocking-aviary1.1?
I should have clarified in my previous comment that on WinXP SP2, unlike the
original reporter's Win98, I get a dialog box when I go to shut down the
computer that tells me that XPCOM:EventReceiver is preventing Windows from
shutting down, and asking me whether to "End Now."  If I do click the button,
(often multiple times, once for each latent firefox.exe process still running),
Windows will finally go ahead and shut down.
not going to block on this without analysis and a patch.
Flags: blocking-aviary1.1? → blocking-aviary1.1-
I saw this when I started to test Firefox 1.5 and 1.6.
Attached file Handle.exe output — 
I use Windows XP SP2 and Deer Park Alpha 2.

This file is output from Handle.exe after I had ended Firefox with exit. Firefox keeps running and if I shutdown the windows I get the error message from the title of this bug. This did not happen with 1.0.x or earlier.

Also if I get updates the firefox can not restart itself. I must kill the process manually and restart it.
hi think this is really a big bug
the community should fix it .....lot of people are thinking to leave firefox

I've been getting this same problem, starting last night, 12/15/05
Web pages become incredibly slow and then availability to Internet stops completely.
If I close FFox and try to reopen, I get a "set up profile" pop-up
Then if I restart pc, I get a "xpcom event receiver" not responding pop-up and have to close manually.

What can we do to stop this lock up when using FFox.
I love the browser and hate to give it up.
Dont know how to tell which version I have, but I upgrade each time they email me, so think it is 1.7
KAT

I have the same problem on Windows 98 running Firefox 1.5, but it doesn't happen every time I run Firefox. Computer also runs VERY slowly when this happens--is this related?
I'm experiencing exactly the same problem, running Firefox 1.5, uTorrent, and
my ADSL connection (actually, the NIC) hangs completely every 10-24 hours.  I
have never gone more than 24 hours a day without a reboot.  This is on Windows
XP with all SPs.  Not running anything else but Firefox and it loses the
network connection - the Network Connection info show the IP address, DNS, etc.
all gone, and traffic slows to a trickle until it dies.

I tried uninstalling Norton Anti-Virus which I found entries as having a probem
with, and used a special utility someone wrote to COMPLETELY remove it, and ran
without for a week and that didn't fix it.

There is definitely something wrong with the XPCOM module, and it hasn't gone away with upgrades.
On an XPSP2 machine, it happened to me almost every day with Firefox 1.5.  It also happened with Firefox 1.501.  It also happens on the same machine with SeaMonkey 1.0, though less frequently - only once in the week or so I've been using SeaMonkey.

Another XPSP2 machine with Firefox 1.5 also gets this almost every day.

I never saw this on either of these machines when running Firefox 1.07 or earlier, nor have seen it on a variety of other machines running Windows 2000, XP, or 2003 with Firefox 1.07 or slightly earlier.
I'm not sure that this will help, but I'm running Process Explorer from www.sysinternals.com and I noticed that when I close FF and the process does not terminate (eventually leading to the XPCOM Event Receiver error), if I look at the open handles for the firefox.exe process, the one handle that I can kill that will  actually let FF continue to shut down and then terminate properly is labeled:

\Device\NamedPipe\Microsoft Smart Card Resource Manager0

It looks like when this handle is terminated, FF goes ahead and goes through a normal shutdown process, at least judging from the sequence that it closes the handles in as it moves toward termination.

I'm running FF on a laptop with a Smart Card reader (O2Micro SmartCardBus Controller).  So, I'm wondering if there is something in the security/authentication code that is causing this to happen.
> 
> I'm running FF on a laptop with a Smart Card reader (O2Micro SmartCardBus
> Controller).  So, I'm wondering if there is something in the
> security/authentication code that is causing this to happen.
> 

After reading this I wondered off to see if a smartcard reader would actually cause this. After trying several scenarios:
a) using the card reader to secure webpage etc
b) not using it
c) removing card
d) using ff with the card inside reader
e) uninstalling the security device from ff
f) same as e) but restarting ff

The solution (for atleast to me) is f) .. removing the security device from ff / thunderbird stopped the XPCOM:EventReceiver from hanging and let ff/thunderbird shutdown cleanly. No more ghost processes hogging up memory and cpu.

This does seem to be an "mozilla" bug since many people seem to have the same problem but with different setups of security devices / drivers / software.

I hope that this information will become handy for someone out there.
(In reply to comment #16)
> > 
> > I'm running FF on a laptop with a Smart Card reader (O2Micro SmartCardBus
> > Controller).  So, I'm wondering if there is something in the
> > security/authentication code that is causing this to happen.
> > 
> 
> After reading this I wondered off to see if a smartcard reader would actually
> cause this. After trying several scenarios:
> a) using the card reader to secure webpage etc
> b) not using it
> c) removing card
> d) using ff with the card inside reader
> e) uninstalling the security device from ff
> f) same as e) but restarting ff
> 
> The solution (for atleast to me) is f) .. removing the security device from ff
> / thunderbird stopped the XPCOM:EventReceiver from hanging and let
> ff/thunderbird shutdown cleanly. No more ghost processes hogging up memory and
> cpu.
> 
> This does seem to be an "mozilla" bug since many people seem to have the same
> problem but with different setups of security devices / drivers / software.
> 
> I hope that this information will become handy for someone out there.
> 

When I reported this bug, I didn't have any TV card, smart card reader, or any hardware out of the norm as far as I can remember. I'm now on Linux and Windows XP 64, and I haven't had it happen since, but I don't think the bug is specifically smart card related. It might just be a general hardware thing, where XPCOM is not releasing hardware. Then again, I have no idea about the internals of XPCOM event receiver, so I might be wrong.
I get the same message as 247827 I run xp windows I get the problem only in firefox version 2. version 1.5 is ok. Geoff
Started getting this error after installing FX2, on two different systems: fully patched Windows 2000 and Windows XP.  Don't have any AV software, use ZoneAlarm.
Except for OS, Bug 309150 is a duplicate of this.  Bugzilla does not have a choice for all Windows.
After upgrading Firefox on Mac OS X to version 2 then the Firefox has started to hang and preventing logouts unless it's forced to quit.
I first have noticed this after upgrading to Firefox 2.0.  Clean install of XP, any earlier version of Firefox was fine, seems to also affect safe mode which rules out extension incompatibility.  When I shut down I have to end XPCOM event receiver about 3 times.  I also noticed at the same time when exiting firefox it remains in memory (the process) and sometimes I have 4 firefox.exe in the task manager when I am only using one firefox window instance

Windows XP Home SP2
p4 3 ghz
2gb ram
Fresh install fully patched
Running AVG Free 7.5
I've recently started also having this same problem after installing Netgear's SC101 storage central.  Even when the service is disabled at startup, it's still appearing.

Configuration looks like this:
Windows XP Pro SP2
1 gig ram
All non-microsoft services disabled.
Assignee: bugs → nobody
I recently started getting this after installing F-secure Internet security 2007, and (possibly) using a web site with an active-x control. Symptom is ghost firefox process after closing, then unable to shut down properly because XPCOM:EventReceiver does not respond. Trying to kill the ghost firefox process with Task manager causes task manager to hang.

There is a workaround in F-secure Internet security which is to uncheck "Enable System Control" in Virus&Spy Protection->real-time scanning->System Control

Firefox 2.0.0.6
Windows 2000 SP4
Blocks: 309150
does anyone believe this problem still exists in v3.x?
(just closed related bug 309150)
Whiteboard: closeme 2009-09-25
I have not seen this happen since I upgraded to v3.5 but I also retired the Dell I was running and have a new machine, so I never figured out if it was FF or a hardware problem - although FF v2.x is still 90% suspicious. But for me, this is closed.
WFM then
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Whiteboard: closeme 2009-09-25
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: