Firefox 32 Arrives With New HTTP Cache, Public Key Pinning Support
An anonymous reader writes: Mozilla today officially launched Firefox 32 for Windows, Mac, Linux, and Android. Additions include a new HTTP cache for improved performance, public key pinning support, and easy language switching on Android. The Android version is trickling out slowly on Google Play. Changelogs are here: desktop and mobile.
Firefox, bagel and lox
Breakfast of champions handy
And aftershave that makes men brave
When over Macho Grande
Burma Shave
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
Just installed the latest Firefox and did a bit of random surfing. First impression: noticeably faster than before, probably even on par with Chrome.
Autoupdated this am.
Seems to work fine.
Memory use seems about the same. (I have 10 tabs open now... lots of "complex/rich" sites... 536 MB)
I don't read your sig. Why are you reading mine?
I prefer FF over other browsers. But it's mainly because it's what I'm used to and the tree style tabs. I'm sure you can get the same for Chrome. But I haven't gotten around to checking.
FF became pretty unstable a few versions ago, though I don't recall which. It seemed to be a memory leak or something. It got up to around 2.5 GB of RAM and then became unresponsive and would eventually crash. My system has 16 GB of RAM, and was never near 100%. The next release took a little longer to reach this point, and the one after that was even longer. I think the version before 32 only crashed once on me. And 32 is open right now as I post this using 2.1 GB of RAM. Granted, I have 13 FF windows open with 5 to 24 tabs open in each.
I post in EVERY Slashdot firefox article, whining for the same thing.
LESS focus on UI / features, MORE focus on stability / performance.
I've been using FireFox since the name it had before FireFox (I've forgotten it) - I think I used it since version 1 or god knows what.
For about the last 12 months, maybe 18, Firefox has become completely unstable for "extreme" browsers like me. I run anywhere from 30 to 150 tabs open at a time. I'd say a nice average would be around 60 tabs. When I'm researching something (often multiple things) I like to google what I'm reading, middle click open in the background the first 5 results. Then when on a forum, I'll middle click open 5 more results and so on. I like having those tabs queued up in the background for me to read.
You might think "well there's the cause of your stability problem!!" except this never used to happen. 18 months ago you could hit 200 tabs without FF crashing. Now, I'm scared to open more than 60. This is across multiple machines too.
I've even tried switching to WaterFox, no dice - I'm still able to crash FF regularly and I run very few addons either.
It's good to see the http cache changes, so they are working on performance but stability should be the #1 focus.
Oddly enough, I get exactly the same symptoms in Firefox for Android as I do Windows for fucks sake. If I hit enough tabs (about 8 on my Galaxy S3) - FF for Android shits the bed, presumably because it's out of ram and can't page well or something. Worst part is FF for Android doesn't remember my open tabs either. Miserable.
They've fiddled and fucked with the UI, replicating Chrome as much as they can (ugh!) for years, now can they stop? If I wanted ugly goddamn chrome I'd install it.
PLEASE fix the stability, PLEASE make it faster. I don't care how much ram it uses, I just want a modern experience with my browser.
Since these updates became more about upping the version number than adding anything really useful and substantive, they should seize this golden opportunity to call it Firefox 100000. Then as the updates roll on from here ...Firefox 100001, Firefox 100010, Firefox 100011, etc.
Firefox mobile: Android 2.2 and ARMv6 processor chipset no longer supported
firefox would have crashed long before i was able to open up that many windows with that many tabs.
after a few hundred pageviews using no more than a few tabs at a time firefox gets close to 2 gigs memory used and stays there.. ui gets sluggish (even more than usual now since the omg-it-looks-like-chrome version), pages start stuttering on scrolling and taking longer to load up in the first place, and acknowledgement of mouseclicks can be delayed so much that what firefox 'clicks' on isn't even what *I* clicked the button on.... this on 8gb quad core win7x64.... and even when running only bare minimum addons like abp and noscript.
and yet i stick with firefox because a) its not google, b) it's not microsoft, and c) adblock and noscript are unequaled still in every other browser
The next time it gets that bad, open about:memory and see what stands out as eating the RAM. There have been issues with AntiVirus software, old crufty features like "ask me about every cookie", the YouTubeCenter addon gobbles up RAM (developer version doesn't), and video drivers with shared RAM being problematic. Adobe has also stopped caring about Flash on Firefox, so that's becoming a real turd in the punchbowl lately. But if you try to dig deeper and help Mozilla find out what the problem is, I'm sure they'll help find out what the cause is. They did for me, so if you're not a total asshat about it, they'll probably help you out too. They do care, they just need someone to help them find the actual problem.
You're right. There's zero excuse for you blaming your problems on Firefox. Since you complained about other people not posting images here you go:
7 tabs open.
1 tab running a video
16 plugins installed
7 extensions running (10 installed).
350MB of RAM used. Go fix your browser instead of bitching about it on Slashdot.
http://s28.postimg.org/3zhxwhuzx/firefox.jpg