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 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.
Firefox mobile: Android 2.2 and ARMv6 processor chipset no longer supported
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.
That's probably a side effect of the "Javascript always on" thing Mozilla did a few versions ago. When they got rid of the "Enable Javascript" checkbox, they also got rid of the options like "Allow scripts to take right-click" and other options.
What's likely happening is your website is blocking right-clicks on purpose (usually as a "protection" measure so you can't right-click and activate extensions like Nuke Anything or Save As).
Of course, the default setting of the checkbox was to disallow websites from hijacking right-click. But since it's gone, so is the setting, so websites are free to hijack right-click.
You need to either use NoScript to block the offending Javascript, or hold down shift when you right-click, which bypasses the right-click hijack and shows the Firefox right-click menu and all the extensions.
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