XPCOM: Event Receiver Problem
-
- Guest
XPCOM: Event Receiver Problem
Hello. I uninstalled 1.5.0.7 and then installed 2.0 from where I have it stored that first day 2.0 came out. The problem I have had off and on is when I close 2.0, got offline, and go to reboot. Up comes a window that says:
"XPCOM: Event Receiver is not responding".
I let it try to shut it down, but it does not work. I then have to hit end program to get out of it and get the reboot. I use XP Home SP2, if this helps. I could not figure this out and uninstalled 2.0 and reinstalled 1.5.0.7, now .8. That cured the problem. What causes that anyone?
"XPCOM: Event Receiver is not responding".
I let it try to shut it down, but it does not work. I then have to hit end program to get out of it and get the reboot. I use XP Home SP2, if this helps. I could not figure this out and uninstalled 2.0 and reinstalled 1.5.0.7, now .8. That cured the problem. What causes that anyone?
-
- Guest
-
- Guest
XPCOM: Event Receiver Problem
I have 1.5.0.7 downloaded and saved. I always do this with Firefox and any other programs.
-
- Guest
-
- Posts: 13808
- Joined: November 7th, 2005, 11:26 am
<b>No, please don't direct people to other sites for downloads. You never know what you are getting.</b> You can always get old files from Mozilla, here: http://releases.mozilla.org/pub/mozilla ... /releases/ .
- dickvl
- Posts: 54164
- Joined: July 18th, 2005, 3:25 am
-
- Posts: 13808
- Joined: November 7th, 2005, 11:26 am
-
- Guest
XPCOM Event Receiver
Okay. First, I did not know where to find the older Firefox builds is why I posted the Hippo url and with the warning that I did not try it.
Second, I have installed 2.0 without removing 1.5.0.8 like another said to do. I tried before taking out the old one and them installing 2.0 and that did not work. Doing it the new way has not stopped the XPCOM problem. I have removed the old profile and put in a new one without any extensions and just my bookmarks. The problem is still here.
What does XPCOM do anyway besides cause problems? No, I do not know is why I am asking.
I am no tech.
Second, I have installed 2.0 without removing 1.5.0.8 like another said to do. I tried before taking out the old one and them installing 2.0 and that did not work. Doing it the new way has not stopped the XPCOM problem. I have removed the old profile and put in a new one without any extensions and just my bookmarks. The problem is still here.
What does XPCOM do anyway besides cause problems? No, I do not know is why I am asking.
I am no tech.
-
- Guest
XPCOM Event Receiver
That was me last post. I mistyped my ID. I saw where it might be Java causing it.
I have Sun Java build 1.5.0_09-b03, the latest update.
I have Sun Java build 1.5.0_09-b03, the latest update.
- greenknight
- Posts: 6187
- Joined: December 13th, 2004, 2:28 am
- Location: In the shadow of Mount St. Helens
Bow 7, XPCOM stands for Cross Platform Component Object Model. As I understand it, it's the framework on which Firefox is built.
This error isn't new to Firefox 2, it's cropped up occasionally on various versions. Unfortunately, I have yet to encounter a reliable solution. Sometimes it just goes away on its own, but that's not much of an answer - wish I had something more. Hard to believe there hasn't been a bug filed about this before.
This error isn't new to Firefox 2, it's cropped up occasionally on various versions. Unfortunately, I have yet to encounter a reliable solution. Sometimes it just goes away on its own, but that's not much of an answer - wish I had something more. Hard to believe there hasn't been a bug filed about this before.
Win 10 Pro x64, AMD Ryzen 5 5600G 6 core, 3900 MHz (4450 Turbo), AMD Radeon Vega (integrated graphics). 16GB DDR4-3200, Firefox 125.0.2, Developer Edition 126.0b5, Nightly 127.0a1.
-
- Posts: 0
- Joined: December 31st, 1969, 5:00 pm
-
- Posts: 0
- Joined: December 31st, 1969, 5:00 pm
- dickvl
- Posts: 54164
- Joined: July 18th, 2005, 3:25 am
XPCOM is the interface that other programs use to communicate with Firefox.
So the error can be caused by other programs that fail to send the proper requests to Firefox and process the answers.
The DOMi does the same (has a DLL and uses XPCOM) and can thus cause that problem as well.
Sometimes the DOMi DLL is still in use when the updater tries to update FX and thus can't replace the DLL with a new version (installer bug, see the sticky at the top of Fx support).
Maybe process explorer (www.sysinternals.com) can tell which external programs use the XPCOM interface.
So the error can be caused by other programs that fail to send the proper requests to Firefox and process the answers.
The DOMi does the same (has a DLL and uses XPCOM) and can thus cause that problem as well.
Sometimes the DOMi DLL is still in use when the updater tries to update FX and thus can't replace the DLL with a new version (installer bug, see the sticky at the top of Fx support).
Maybe process explorer (www.sysinternals.com) can tell which external programs use the XPCOM interface.
-
- Guest
XPCOM Event Receiver
Greenknight and Dickvl - Thanks for the info.
Now, I may have cured it on mine. I made a new profile, without any extensions, put it in and removed the original. It was still doing it. I then installed GetMail and IEViewLite. I have not had the problem since. So far, 2.0 is running fine. I have my fingers crossed.
Thanks to all who placed links on and info to help me track down my problem.
Now, I may have cured it on mine. I made a new profile, without any extensions, put it in and removed the original. It was still doing it. I then installed GetMail and IEViewLite. I have not had the problem since. So far, 2.0 is running fine. I have my fingers crossed.
Thanks to all who placed links on and info to help me track down my problem.