firefox crashing windows
Matthew
firefox updated itself to version 3.0.2 windows crashed. Every computer
in my office that has done that update has crashed. This really sucks.
Anyway. The error i'm getting is 'The application failed to initialize
properly (0xc0000022). Click on OK to terminate the application.' It's
doing this on everything and on every user account.
Anybody else experiencing these problems?
Jay Zie
> Anybody else experiencing these problems?
naw dawg
Frank McCallister
--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC
"Matthew" <n...@no.com> wrote in message
news:Opeyk.6016$gS5....@kovat.provo.novell.com...
Greg B
Matthew
> Did you try starting FF in safe mode?
>
You can't. Nothing works. Firefox hosed up the entire system. I can't
get into anything. Same error on everything. I know it's firefox
because I tried it on a computer that was working just fine. Opened up
firefox and the system crashed. Firefox 3.0.2 is broken. Don't use it.
Jay Zie
Did, and it's working fine for me.
Matthew
You will. Don't allow firefox to update.
Matthew
did you install in or allow it to auto update?
Matthew
> Matthew wrote:
>
>
>
>
> http://www.pctipsbox.com/fixing-the-firefox-memory-leak/
It's not a memory leak. It some how screwed up file permissions or
something. I'm not real sure. I'm starting to see the same problem on
the internet. My advice to everybody is don't update firefox and turn
off the auto update.
Jay Zie
Matthew
Jay Zie
Matthew
Matthew
Adam Gabriel
> It's not a memory leak. It some how screwed up file permissions or
> something. I'm not real sure. I'm starting to see the same problem on the
> internet. My advice to everybody is don't update firefox and turn off the
> auto update.
Maybe its some of the sites you're visiting with firefox that are hosing up
your pc... ;-)
--
Matthew
failed) I was able to get it working again. According to the system
restore and unassigned driver was installed, but it was at the same time
firefox was updated. I don't know what to think about that. :(
Donald Albury
<buchanan.n...@gmail.mapson.com> wrote:
>http://www.pctipsbox.com/fixing-the-firefox-memory-leak/
The memory leak problem was prior to FF 3. It's less of a problem since I
upgraded to FF 3.0.1.
Donald Albury
Michael Bell
BTW AFAIK there is no 3.0.2
Barry Schnur
Not a released version -- but a late pre-release version is out there.
3.02 is supposed to be released later this month. Then behind it there
is a 3.1 which should be more of a change.
--
Barry Schnur
Former Novell Support Connection Volunteer Sysop
Matthew
so you can understand why I jumped the gun on Firefox being the cause of
my problems. Today is a good day.
Here's what I discovered. Firefox was not the root of all my evil.
ESET NOD32 was. I don't know what happened yet, but apparently one of
it's updates made it think everything was evil on my computer.
For my own future reference. Check AV first.
--
Matthew - The Great System Tyrant
--------------------------------------
http://www.mattography.net/
http://www.matthewdgood.com/
http://www.systemtyrant.com/
Patrick Farrell
> First let me say that yesterday was a bad day for a great many reasons
> so you can understand why I jumped the gun on Firefox being the cause of
> my problems. Today is a good day.
>
> Here's what I discovered. Firefox was not the root of all my evil. ESET
> NOD32 was. I don't know what happened yet, but apparently one of it's
> updates made it think everything was evil on my computer.
>
> For my own future reference. Check AV first.
>
>
Darn, I was hoping to blame Microsoft :P
Patrick Farrell
Patch Tuesday get ya?
Matthew
Well, it's easy to blame Microsoft. If their OS was more secure, like
the Mac, then you wouldn't need AV. No AV no problems. :P
Patrick Farrell
> Patrick Farrell wrote:
>> Matthew wrote:
>>> First let me say that yesterday was a bad day for a great many
>>> reasons so you can understand why I jumped the gun on Firefox being
>>> the cause of my problems. Today is a good day.
>>>
>>> Here's what I discovered. Firefox was not the root of all my evil.
>>> ESET NOD32 was. I don't know what happened yet, but apparently one
>>> of it's updates made it think everything was evil on my computer.
>>>
>>> For my own future reference. Check AV first.
>>>
>>>
>>
>> Darn, I was hoping to blame Microsoft :P
>
> Well, it's easy to blame Microsoft. If their OS was more secure, like
> the Mac, then you wouldn't need AV. No AV no problems. :P
>
>
Well duh, everyone knows Mac's never have security updates! :p
DZanre
> Well duh, everyone knows Mac's never have security updates! :p
well, they do, but usually in ADVANCE of problems <g>
--
Danita
http://www.caledonia.net/blog
Patrick Farrell
> Patrick Farrell wrote:
>
>> Well duh, everyone knows Mac's never have security updates! :p
>
> well, they do, but usually in ADVANCE of problems <g>
>
That's almost more sarcastic than my post..
DZanre
> That's almost more sarcastic than my post..
heehee - I thought you might like that.
That said, I certainly haven't worried much about my MAC overall.
--
Danita
http://www.caledonia.net/blog
Patrick Farrell
> Patrick Farrell wrote:
>
>> That's almost more sarcastic than my post..
>
> heehee - I thought you might like that.
>
> That said, I certainly haven't worried much about my MAC overall.
>
Now we'll see if Chrome takes as long to fix the carpet bombing
vulnerability as safari did. Of course it should have learned from that
mistake before release but we won't go there.
Barry Schnur
> ESET NOD32 was. I don't know what happened yet, but apparently one of
> it's updates made it think everything was evil on my computer.
>
have a bad hair day.
Matthew
>> Here's what I discovered. Firefox was not the root of all my evil.
>> ESET NOD32 was. I don't know what happened yet, but apparently one of
>> it's updates made it think everything was evil on my computer.
>>
> Interesting -- I run NOD32 here on a lot of computers - -they didn't
> have a bad hair day.
>
>
>
They are all good now. The next day after it updated again all the
problems went away. I use custom Windows images (nlite) and it might
have been something with it that was causing the problems. At this
point... who knows. :P
Barry Schnur
> problems went away. I use custom Windows images (nlite) and it might
> have been something with it that was causing the problems. At this
> point... who knows. :P
OK -- it does happen -- I saw the mess with the McAfee update last week.
jahn...@gmail.com
> I won't say for sure that it's what caused it, but it appears that after
> firefox updated itself to version 3.0.2 windows crashed. Every computer
> in my office that has done that update has crashed. This really sucks.
>
> Anyway. The error i'm getting is 'The application failed to initialize
> properly (0xc0000022). Click on OK to terminate the application.' It's
> doing this on everything and on every user account.
>
> Anybody else experiencing these problems?
I did an error doing a scan with AV program that referred to "CORE" IN ff. regretfully, I did not write down the reference and have been unable at this time to reproduce it.