Closed Bug 249805 Opened 20 years ago Closed 3 years ago

XPCOM:EventReceiver appears to hang program and hold dialup component

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: r_rom, Unassigned)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Build Identifier: Firefox 0.9.1

There have been several instances by now in which I am unable to dialup to
access the Internet (with an error message saying something about the dialup
module being used by something). To solve this, I reboot my computer, which is
when I get a dialog box asking me if I want terminate XPCOM:EventReceiver. Task
manager shows that Firefox is still an active process despite the fact the I had
previously told Firefox to exit.

I don't know how to reproduce it, but it has happened several times with
previous versions and one time with 0.9.1, which I installed one or two days ago.

There's one thing I'd like to add: I frequently allow Firefox to stay active
when I make my system hibernate.

Reproducible: Sometimes
Steps to Reproduce:
I'm getting this also with an ADSL connection - Firefox (Mozilla and Thunderbird
also) will "hang" the connection from the machine they're running on (not an
issue from other machines - the connection is still active).  Rebooting seems to
be the only solution, and as reported "XPCOM Event Receiver" will not close on
it's own.
I just lost ability to establish connection to the Internet via dial-up (I was
getting the same message I reported originally -- something about modem or port
being in use already). I had many programs open and decided to find out if any
of them was responsible with the problem. Well, by closing one by one, I
determined that it was Firefox (0.9.3). Once Firefox was out of the way,
everything started to work again.

I wish we had a tool to extract runtime data from the browser to help
troubleshooting problems.
Since installing 20041207 build of Thunderbird, I cannot reboot Windows anymore.
I get a message that XPCOM:EventReceiver will not close.
Severity: critical → blocker
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to comment #3)
> Since installing 20041207 build of Thunderbird, I cannot reboot Windows anymore.
> I get a message that XPCOM:EventReceiver will not close.

I've got the exact same problem here.  I'm running Windows XP SP2, Firefox 1.0,
and Thunderbird 1.0
This also happens with current Mozilla trunk builds it seems (i can't reproduce
it, but i've read from people that can).
Assignee: firefox → dougt
Component: General → XPCOM
Product: Firefox → Core
QA Contact: general → xpcom
Version: unspecified → Trunk
I think that this is related to bug 247827.
Experiencing exactly the same problem, running Firefox 1.0.7, BitComet, Microsoft Outlook at the same time on Windows 2000Pro SP4 platform. Having checked thoroughly for trojans, viruses etc., I also ascribe unexplained but regular fluctuations in CPU usage to this bug.
I'm experiencing exactly the same problem, running Firefox 1.0.7, 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.
I see this problem as well.  I'm running Firefox 1.5.0.6 on Windows XP SP2.  I initially thought it was a McAfee firewall/virus scan issue but I uninstalled that software and the problem still happens  Note: I am using VPN software (VSClient).

After a certain amount of time all network traffic is DEAD, I can't browse to any sites, and I have to reboot the computer.  Sometimes I have to turn off the power because the system cannot shutdown due to stuck XPCOM:EventReceiver processes.

I also experience XPCOM: Event Receiver hang up on close down.  Have to manually "end event" as many times as I have opened Firefox since turning computer on.  I'm using Win XP w/SP2, no other special programs.  Began to see bug as soon as I updated to latest version of Firefox.  Haven't had time to go through multistep process of creating new profile, etc.

Is there an identified cause and ready fix before I go through all that?
Nope, these is no identified cause, althuogh in another bug report someone spent a lot of time (I think his name was "Moop") tracing the stack to showing exactly what WAIT_STATE was getting stuck, possibly some sort of race problem.

More importantly, there is no fix, and dozens of bugs entered against this, but as of yet, no progress on addressing the problem, much less fixing it.  I've dealt with it since Firefox 0.9 up to Firefox 2.0.5 and I continue to have the problem, in fact it's merely become more frequent.

Sorry to be the bearing of bad tidings, Charles.
After having switched to broadband connections, I don't remember having this problem.
mass reassigning to nobody.
Assignee: dougt → nobody
Recently had XPCOM:EventReceiver hang in Firefox 2.0.0.14 in WinXPSP3 with broadband connections(LAN+WiFi).

Unfortunately can't surely say if connections themselves were still working, didn't try to restart them too.
Firefox version 3.6.8; OS Win 2000

I will speculate that this problem is not a dialup issue.  However, because ethernet connections are "permanent", so to speak; the users have either not seen it or when encountered the issue, they have assumed a stuck network adaptor and have rebooted their system.
This is my reason:
1) This link shows the process and task bar icons after boot up.  My system has a WiFi and an ethernet LAN adaptor; neither used here.
       http://info.paperlessprocess.com/Firefox/1_Startup_No_Connection.jpg

2) This link shows a normal dialup process and icon.
       http://info.paperlessprocess.com/Firefox/2_Dialup_only.jpg

3) This link shows a normal dialup plus VPN connection and their icons.
       http://info.paperlessprocess.com/Firefox/3_Dialup_and_VPN.jpg

Note:
         a) Should I close the dialup, both dialup and VPN will disappear, back to item 1) above.
         b) Should I close the VPN only, the VPN process and icon disappears and system shows item 2) above.
         c) I started and stopped Firefox many times and used it in a normal way.  Until after one of the starts I saw "server not found" message.  Please proceed:

4) This link shows that the VPN process is alive, but its icon gone.  A problem that only Firefox usage can cause.  Thunderbird has never created this situation.
       http://info.paperlessprocess.com/Firefox/4_Dialup_with_VPN-gone.jpg

5) This link shows that by closing the dialup, both its process and icon will disappear.  Something that is different from the original report of this trouble ticket.
       http://info.paperlessprocess.com/Firefox/5_No_Dialup_but_VPNprocess.jpg

So I conclude that the problem reported is correct and Firefox does mess-up the connectivity adoptor or processes.  However, because my dialup, as demonstrated in link 5 could be shut down normally, and because the problem can be shifted to a VPN process, this problem (with and without VPN) must be reproducible under ethernet LAN connection.  Any volunteers?  :)
Putting Thunderbird and Netscape 7.1 through above process (comment 15); I was not able to cause any harm.  Connections would close properly and a restart of these programs would connect to internet every time.

It should be noted that Firefox will do it within a dozen tries, but I do not have a reliable sequence to cause it on the first try.
(In reply to comment #16)
> Putting Thunderbird and Netscape 7.1 through above process (comment 15); I was
> not able to cause any harm.  Connections would close properly and a restart of
> these programs would connect to internet every time.
> 
A correction to my previous comment.  After three months of watching, today Thunderbird version 3.1.2 also did it.  That is, I booted the PC, dialed into server, started Thunderbird, did receive and send e-mails.  Then shut down the dialup connection.  Looking at "Windows Task Manager" Network Tab showed the Telephone line process that was still alive.  Subsequent dialup would connect to server but not connect to Thunderbird.  (Firefox was not running.)

This tells me that the problem is in both products and I still maintain not in dial up alone, but it shows most often in Firefox dialup condition.
(In reply to Parkhideh from comment #17)
> A correction to my previous comment.  After three months of watching, today
> Thunderbird version 3.1.2 also did it.  That is, I booted the PC, dialed
> into server, started Thunderbird, did receive and send e-mails.  Then shut
> down the dialup connection.  Looking at "Windows Task Manager" Network Tab
> showed the Telephone line process that was still alive.  Subsequent dialup
> would connect to server but not connect to Thunderbird.  (Firefox was not
> running.)

Parkhideh, but it does not hang, correct?
Severity: blocker → critical
(In reply to Wayne Mery (:wsmwk) from comment #18)
> Parkhideh, but it does not hang, correct?

Wayne, if by "hang" you mean PC stops working, then "No it does not hang"; however, as mentioned, the subsequent dialup is of no use.  Because a forth process starts, now one sees TWO dialup processes in "Windows Task Manager" Network Tab, and no application can connect to it.
I have not found a method to kill the original dialup process, or to redirect the applications to the new dialup process.  It appears that they are all threads of SVCHOST.exe
Andrey writes "I saw it only once, 3 years ago. And I didn't use dialup connection (unlike others) when it happened. "
Rob writes "I'm at FF 6.0.1 and haven't seen it since FF 4.x."
(In reply to Wayne Mery (:wsmwk) from comment #21)
> Rob writes "I'm at FF 6.0.1 and haven't seen it since FF 4.x."

(In reply to Wayne Mery (:wsmwk) from comment #20)
> Andrey writes "I saw it only once, 3 years ago. And I didn't use dialup
> connection (unlike others) when it happened. "

Wayne,
   In comments 15 and 17, I reported seeing this problem in VPN (without a dialup) and in Thunderbird with dialup.  So what Andrey writes is possible.  Now I will use version 6 Portable Firefox and version 7 of Firefox to see if the issue is resolved or buried deeper.  Currently this problem shows up about once out of seven sessions of Firefox with Thunderbird combined.
Firefox version 7.0.1 testing (sorry if duration of test is not up to par):
Downloaded Firefox version 7.0.1 and ran it a few times with connecting and disconnecting the dial up.  It worked every time.  (Too short a test)
Then went about my business, running Thunderbird version 3.1.2 and Firefox; now disconnecting the dialup did have the problem.

This comment is more than anything for sake of those who may have upgraded Firefox to version 7 but not the Thunderbird.  Instead of my approximately one in seven tries that caused the dialup problem in Firefox v 3.6.8 (with and without Thunderbird), combination of Firefox 7.0.1 and Thunderbird version 3.1.2 does hang up the dialup once in three tries (it happened for several days).

So, upgraded the Thunderbird to version 7 (because I read something is new in the Mozilla engine 7) and I have not seen the dial up issue when both are version 7 (over a week of using).
(In reply to Wayne Mery (:wsmwk) from comment #21)
> Rob writes "I'm at FF 6.0.1 and haven't seen it since FF 4.x."

Unfortunately I spoke too soon.  The problem is with us when using Firefox 7.0.1 and Thunderbird 7.0.1, although not as often as version 3.

My crude observation is that Firefox version 3 was causing the problem once a week, version 7 is showing the problem once every three weeks.

A suggestion: since the combination of Firefox v7 and Thunderbird v3 does it more often (on my setup), this may be a better combination for developers to catch the bug.
Firefox 7.0.1 and Thunderbird 7.0.1
The problem has shown itself again.  So it is still with us.
Again, I have not seen it by running one product alone, mainly because my work requires both and I do not spend much time with one without the other.
(In reply to Parkhideh from comment #25)
> Firefox 7.0.1 and Thunderbird 7.0.1

I will add to comment 25 that every time the above programs ran for over six hours, the problem showed up.

1- Firefox:  The sites that was visited:
  a) www.bbc.co.uk and links thereof; but no flash or other multimedia effects. 
  b) http://games.yahoo.com/sp  which has much Java Applets.

2- Thunderbird:
  a) Receiving POP mail notices automatically for 5 accounts from various ISPs, then manually downloading one account at a time, using Get Mail and selecting the account.

Concurrently one Visual Basic program was also used to access the internet.  Excel is also used as a local application without permission to access the network.
Firefox version:  None;  Thunderbird Version:  None;  :)
Application: WS_FTP Pro version 6.6;  www.ipswitch.com

I had to upload a large file over dialup and it took several hours.  After closing the application and the dialup; as it has become second nature to me, the TaskManager / Networking tab was checked; and you guessed it, the dialup process was alive.  No Firefox or Thunderbird in sight.  Session was started by booting the PC and immediately running WS_FTP to upload.  So where is the problem?  My system, Windows OS or is Ipswitch using the same method as Mozilla when connecting to a dialup process?

Please note that I am a blackbox tester.  So visit comment 15 and there my speculation was that dialup is not the issue.  Now I shall improve on that.  I think Windows OS may have an issue when dealing with processes that do not permanently exist as part of the resident OS.  My Ethernet and WiFi are always there under TaskManager / Networking (even though there is no signal/connection).  So users of Ethernet and WiFi will not see this bug no matter how many times the connection breaks and reconnects.  Because of, and I speculate, the process being always alive.

But VPN and Dialup processes are not always there.  So did my FTP program run the same course as the VPN process of comment 15?

[A side comment: when you do not want to know of a problem, don't look for it.  I have used WS_FTP Pro for the past 12 years and never checked.  :)  ]
To conclusively prove that this is not a dialup issue; I connected my PC to an ethernet port that has internet connection on its LAN.  Did not used WiFi or Dialup in the last six weeks.

As expected, everything works fine because the Local Area Connection is a permanent service of Windows OS.  But starting a VPN is not a permanent connection and task manager shows it when connected and "should" remove the process when disconnected.

Disconnecting VPN sometimes makes the process go away, and sometimes the process stays alive.  It can be seen on Windows Task Manager / Networking tab as a graph.

When the VPN connection stays alive (while disconnected); no further internet activity is possible.  Starting a new VPN will not correct the situation.  PC must be rebooted.
Parkhideh, which product and version are you using?
(In reply to Roman R. from comment #29)
> Parkhideh, which product and version are you using?

Firefox 16.0.2
Thunderbird 16.0.2
WS_FTP Pro  6.60  (very old)

Problem occurs with using one or a combination.  But it has not been reproducible in any systematic way.

Since the last comment here is 9 years old and Windows XP is no longer supported, I will close this issue as incomplete.
In case this is still reproducible using more recent versions of Windows, please feel free to re-open with further info.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.