Slashdot Mirror
Is Firefox 1.0 Less Stable than Firefox PR1.0?
An anonymous reader wonders: "I had Firefox 1.0PR running smoothly on three different machines and it hardly ever crashed. After upgrading to 1.0, I seem to have at least one annoying crash a day. On one of the machines, using the 'self update' feature caused Firefox to crash in middle of the upgrade and left it in a completely unusable state. Eventually, I had to uninstall it and resort to using IE to download the full installer, again. Is it just me, or are other heavy Firefox users noticing this sort of behavior?"
Why don't you try posting on the Mozilla.org forums?
My PR Firefox version Firefox/0.9.3 has always had the annoying problem of causing the entire system to "lock up" if left running overnight. (Win XP SP2.)
Ignorance is curable, stupid is forever.
Up until now, under windows xp sp2, firefox 1.0 final is running very smoothly, no crashes, im using it all the time.
Under linux also, there are no issues, exept maybe with the mplayer-embedded plugin, but that is the plugins fault actually, experiencing the same problem with epiphany, konqueror and opera. So no, from my point of view firefox is as good as it gets!
pass me those sparticles will ya?!
No problems whatsoever. The search function finally works and updates are a breeze. On my Windows and Mac machines. HOWEVER, my Linux box was not quite as rosey. I upgraded my source-built FireFox 1.0PR to FireFox 1.0 binary. I unmerged the 1.0PR and downloaded the binary from the FireFox website, installed it, and rebooted. At first, things were smooth sailing, but after an hour or two of usage, FireFox would become unusable and eventually crash. Same problem under SuSE. I uninstalled the binary and emerged FireFox 1.0 from source and everything was great.
"You and your third dimension."
Make sure you uninstall any old versions before installing the new version. Its in the faq.. well hidden, but i've had no problems when uninstalling then re-installing. Make sure to back up, but your savings should be saved as they are not held in the same area as the executeables and whatnot. I have had problems just upgrading, but i've been problemless since i've done the above.
"We are eternal.. all this pain is an illusion." -Maynard James Kenan
Go to CNN. View a few stories. **CRASH**
This is:
Linux 2.6, GNOME, 32-bit ppc, libswf installed,
multiple windows open, Debian-unstable, the tab
preferences extension installed so I can go back
to the old pre-tab Mozilla ways...
This really, really, sucks. I was one of those
people that would keep a browser running for
several weeks at a time. I'd let it sit on one
virtual desktop with two dozen windows open.
This is something that instead of being asked here should be asked at the Mozilla Firefox forums. There are lots of people who will be happy to help you.
If you believe you have found a bug, you should search if anyone has reported that bug, and if not report it here.
Sorry, but its almost offensive to see this at slashdot.
That could possibly be the situation. I know I uninstalled all the extensions which were not compatiable with 1.0. PR1 crashed a whole lot more than 1.0. Actually, I don't think its crashed yet.
Also, something you might want to do is to create a new agent. Just make sure you save your bookmarks.
It is a well known bug. The fix is in the current gecko devel tree. The quick workaround is to hit ctrl- followed by ctrl+. The shrinks then expands the text on the screen. It also causes the text to reflow correctly.
I much prefer to hold down CTRL and then scroll the mouse wheel up, then down. Does the exact same thing, just easier than taking my hand off the mouse ;)
Ditto, 1.0pr had a very annoying habit of crashing when I was using multiple tabs or when I opened a pdf in a new tab.
FireFox only crashes on me when I've been using Java for awhile. It has always happened with all the Mozilla products. I upgraded to Java 1.5 thinking this Java issue would stop crashing my browser, but it keeps doing it.
I must agree. I have had many different identities and have been around since very close to the beginning (damn master passwords - always make me lose passwords!). As far back as I can remember people have been complaining about this very issue. Actually /. has stayed relatively the same over the years IMHO, other than a few joke evolutions :)
I am running SuSE 9.1 (frehsly installed) and did run firefox pre for quite some while. The only problem I ever had with it was the "auto find as you type" - it would always kick in when you type a "/" in a input box (which is annyoing in webchats!). I already did disable it, set the timeout to really low etc, but 10pre would always open the "find" bar when I started with a "/" - annoying!
Then I installed v1.0 - the "find-as-you-type" bug is gone - yeah!
Unfortunately, about once a day I manage to crash firefox - something which almost never happened with 1.0pre.
So, yes, 1.0 is less stable. However, it didn't occur to me to whine somewhere about it, because that is not going to help.
Tels
I've done several upgrades of Phoenix, Firebird and now Firefox on different machines, and I have grown accustomed to letting the new version create a new profile and then copy the stuff you still want back into it. I normally delete "C:\Docs and Settings\MYNAME\Application Data\Mozilla\Firefox", then copy the old bookmarks.html into my profile again.
Did so with PR1 -> 1.0, and have had no issues on several machines.
For some reason many times the page is not rendered in a way I can read. the columns in slashdot often overlap, and are really weird. in IE all is fine
yes I do see the irony
well, i had an opposite problem. 0.9 and 1.0PR were crashing all the time, 1.0 is rock solid. i use Mac OS X 10.3.6.
1.0PR had a javascript pop-up crash bug that drove me crazy. 1.0 fixed that.
Some things to consider:
1. How did you install 1.0? Did you do an overwrite? If so, do a clean install.
2. What extensions are you using? Have you disabled the extension version check?
>On one of the machines, using the 'self update' feature caused Firefox to crash in middle of the upgrade
When was this? Do you have DNS/network/firewall issues which could be causing this?
Lastly, to get some real answers from the experts people should asking here.
Another problem that it could be (one that I had, anywho) is preferences for an extension that had been previously uninstalled.
Example: I installed an extension during the PR release. I found that I didn't really like it, so I uninstalled it and carried on without a problem. 1.0 is released, downloaded it, installed... FF now crashes every 30 minutes or so.
Skip over a large chunk of trying to figure out what the hell is going on, and I found some leftover files and preferences (prefs.js) from the aforementioned extension in my profile folder. Deleted those and everything was back to being peachy.
http://www.hardgrok.org/blog/item/slashfix-firefo
Isn't open source great?!
"City hall" in German is "Rathaus" Kinda explains a few things......
do you leave firefox in a page with flash animations? nowadays many of the animated figures in a web page are flash and not animated gifs anymore. a badly made flash can take up tons of CPU even when you leave it there. also, are you viewing web sites with automatic page refreshing? it will eat up the CPU everytime the page refreshes.
if that bothers you, you can always use the task manager to set the process's priority to either "below normal" or "low".
however, games are memory intensive. so as a browser, which uses memory caching to be fast. when real memory is used up, "thrashing" occurs (to swap some memory pages to the disk). even adjusting task priority won't help here, since thrashing is inherently slow. whenever a web page that you leave in the background refreshes itself, the OS has to swap out a few pages of game memory and swap in memory pages for the browser. as the game continues, it needs the memory back, and the OS has to juggle around memory pages again.
if you see a periodic frame loss, then self-refreshing web pages are definitely the culprit.
I once had a signature.
I think all computers should have at least two nipples
There are two keyboard nipples. That's what the little bumps on the "F" and "J" keys are. They are there so you can position your fingers on the keyboard for typing without looking. I think the grandparent poster was referring to a trackpoint mistakenly as a keyboard nipple.
Try uninstalling Firefox 1.0PR, don't worry the profile will be left intact, then install Firefox 1.0, this works just fine, and Firefox 1.0 is completely stable.
I had similar problems back with the last 0.9.whatever release. After I thought about it a bit, I ran Ad-aware and Spybot. BINGO! Three new spywares detected! (I may have gotten a tad over enthusiastic looking for new plug-ins.)
Seems that they expected IE, and bollixed Firefox trying to do their dirty deeds.
Lessons learned:
1) Only accept plugins from known safe sources. (https://update.mozilla.org/extension)
2) Firefox is a great browser, but it ain't idiot proof! (And Even I can be an idiot if I don't think first!) };-)
3) The number of people that'll yell at you when you ask an honest question, instead of offering help, is discouragingly high.
The U.S. really needs an English to Wisdom dictionary.
It's not just any OS updates. Mozilla and Firefox lockup quite regularly on my Linux system starting very recently. I doubt this particular problem is an M$ conspiracy since I don't do M$ updates to my linux box.
That said, I think the problem lies with the flash plugin more than Firefox. I updated today and the same links that locked Mozilla (and Firefox) before don't do it anymore. Of course, you may have a different problem...
Well, the validation works fine from Opera. I get 227 errors on that page, and something about it not being valid HTML 3.2.
Some of the errors are:
Line 8, column 14: there is no attribute "TYPE"
Line 38, column 11: there is no attribute "TOPMARGIN"
Line 38, column 26: there is no attribute "LEFTMARGIN"
Line 39, column 13: there is no attribute "MARGINWIDTH"
Line 39, column 30: there is no attribute "MARGINHEIGHT"
Line 43, column 8: there is no attribute "BGCOLOR"
It goes on...
Opera, Proxomitron-Grypen,GPG 0x0A1C6EE3
I had this problem previously with a much earlier release of firefox. What I did to fix the problem was back up my bookmarks, go into the application settings hidden folder under the user name you are logged in as, and find the folder for firefox and delete it. Then open the browser again, and the browser will create a new temporary settings folder. Then just restore your bookmarks and you will have it working again without problems. Firefox 1.0 runs great for me.
Firefox 1.0 initially acted like a giant steaming pile... I then blew away my profile from pre 1.0 (saving bookmarks), and started over, and it has been great ever since... Not necessarily what you want to have to do, but I'll accept it since it was technicall 'pre-release' until now.
XML is like violence. If it doesn't solve the problem, use more.
If Tyranny and Oppression come to this land,
it will be in the guise of fighting a foreign enemy. -James Madison
uhh, try mozilla 1.7.3 - works fine.
ôó
Actually it's a synaptics touchpad hardware/driver feature. The touchpad normally emulates a PS2 mouse; however, there is a 'raw' mode that you can put the hardware into that basically returns the position of the user's finger on the pad. This allows you to do a lot of different things in software such as simulate a scroll wheel when the user tracks up and down the right edge, horizontally scroll when the user tracks on the bottom edge, perform browsing back/forward actions on the top edge, simulate extra mouse buttons with corner taps, etc.
A really really good implementation of a raw-mode synaptics driver is available for MacOS as SideTrack. It used to be free while it was in beta. Now it is $15 and a heck of a good deal. It fixes the powerbooks' problem of lacking a right mousebutton and scroll wheel while giving all sorts of extra enhancements that really make that one button mouse a lot more usable.
...I had a problem when using the auto-updater. But with a few quick Google searches I was able to simply delete a few profile-related files (not my profile itself) which fixed the problem (and the files were recreated automagically by FF). Overall, 1.0 has been much more stable for me than 1.0PR. When I upgraded from 0.9 to 1.0PR, I suddenly started having crashes on an average of 2-3 times a day. Since going to 1.0, I don't think I've had a single crash.
If it's a display issue, the excellend AdBlock extension may help out.
Since I know that technically, nipples on the keyboard refer to the bumps on the F and J (D and K for Mac users), I accept "clitoris" as the appropriate term for that bump.
I've never understood why the bumps on the F and J are referred to as nipples. They're so much smaller.
www.timcoleman.com is a total waste of your time. Never go there.
Slashfix has been downloaded by over 5000 people in the last week. I've received dozens of messages of thanks and 3 or 4 people have complained that it didn't work. I've already explained several times that this is pretty much impossible - the fix consists of about 10 lines of Javascript. This isn't some magical complex app, it's either gonna work or not, and for 99.9% of people it works, so I must assume the problem isn't in the code.
Most likely FF is hanging on pageloads or something - are you actually waiting for the page to finish loading? Are you loading tabs in the background? Because my site already documents the limitations to the fix (it runs only when the pageload event is triggered, namely when a page finishes loading, and tabs loaded in the background never trigger a pageload). I am of course perfectly open to suggestions or enhancements. If the limitations annoy you, feel free to work around them, it's perfectly possible, just takes some effort and toiling with the Firefox extension API stuff. Maybe you should get off your butt and help instead of whining?