- Joined
- Jul 6, 2010
- Messages
- 17,704
- Tagline
- Broken beyond repair but highly affable
First of all, FF 65 in 32 bit was always crashing like a drunk driver, mainly on MSN or Yahoo.
So FF 66.0 was released last week, it didn't change much. Maybe crashed more.
I'm dealing with a 32 bit Dell and Windows 7 here of course. 6 GB of 800 MHz RAM IIRC.
Core2 Duo 6300 at 1.86? GHz per core. Sorta Rihanna and not Madonna.
Emily to be exact. 2006ish
Okay, I know what is happening when FF hangs and forces a hard shutdown...at least one of the e10 processes gets really full, sometimes 1 GB.
Now, 66.0 came out and the default number of e10 processes was DOUBLED to EIGHT. That only froze it 2x as fast.
Now if I have to be blunt, I could leave open 50 pages of porn with some being video and it would run for hours but two sites kill it?
Suuuuure.
But here is the doozy...
Yesterday they apparently released a patch, 66.0.1 and it involved two critical exploitable memory issues, which may have also been around for a while and could cause buffer overflows that might have been related to my problems.
But 64 bit worked much better. Still. My other two 64 bit machines are running Linux, unless I can get a license for Wylla, and I'm reluctant to use Linux Mint on her for the so-far lack of drivers for card readers that I have. What is the point of that?
None of this stuff is going to run 10 well, not even Alison now. I have FOUR running computers and I'm working on trying to get Valerie going again in a new case, just to save the Win 7 drive. I blew a few chunks out from her fan shroud's base after buying another can of air this month. Hyperthreading 2.6 GHz P4 or not, that Intel 965 will either live or die.
And I reset the 310 for 2 instead of four eqos, It doesn't really matter as the Task Manager still lists 5 or more Firefoxes...okay FOUR and not much over 120K right now.
I'll have to do some 'power' usage for a while today and see what happens, if two sites are still killing me and what more to do.
Just do me a favor and don't try and tell me Chrome is so freaking better, I don't care. I give them You Tube and that's about it.
So FF 66.0 was released last week, it didn't change much. Maybe crashed more.
I'm dealing with a 32 bit Dell and Windows 7 here of course. 6 GB of 800 MHz RAM IIRC.
Core2 Duo 6300 at 1.86? GHz per core. Sorta Rihanna and not Madonna.
Emily to be exact. 2006ish
Okay, I know what is happening when FF hangs and forces a hard shutdown...at least one of the e10 processes gets really full, sometimes 1 GB.
Now, 66.0 came out and the default number of e10 processes was DOUBLED to EIGHT. That only froze it 2x as fast.
Now if I have to be blunt, I could leave open 50 pages of porn with some being video and it would run for hours but two sites kill it?
Suuuuure.
But here is the doozy...
Yesterday they apparently released a patch, 66.0.1 and it involved two critical exploitable memory issues, which may have also been around for a while and could cause buffer overflows that might have been related to my problems.
But 64 bit worked much better. Still. My other two 64 bit machines are running Linux, unless I can get a license for Wylla, and I'm reluctant to use Linux Mint on her for the so-far lack of drivers for card readers that I have. What is the point of that?
None of this stuff is going to run 10 well, not even Alison now. I have FOUR running computers and I'm working on trying to get Valerie going again in a new case, just to save the Win 7 drive. I blew a few chunks out from her fan shroud's base after buying another can of air this month. Hyperthreading 2.6 GHz P4 or not, that Intel 965 will either live or die.
And I reset the 310 for 2 instead of four eqos, It doesn't really matter as the Task Manager still lists 5 or more Firefoxes...okay FOUR and not much over 120K right now.
I'll have to do some 'power' usage for a while today and see what happens, if two sites are still killing me and what more to do.
Just do me a favor and don't try and tell me Chrome is so freaking better, I don't care. I give them You Tube and that's about it.