Avast WEBforum
Other => General Topics => Topic started by: polonus on March 05, 2006, 02:00:48 AM
-
Hi forum members,
Firefox 2.0 is soon to be out. Will it be another memory hog, will it crash while you try to scroll a loading page. For the moment I stay withFlock, other may go back to Opera. Are the changes worth the change from 1.5 to 2.0? This is the roadmap proposed:
http://wiki.mozilla.org/Firefox:2.0_PRD
polonus
-
Hi Polonus,
It's difficult to say what will happen if anything with the new version of Firefox. I have stayed with Firefox version 1.07 after trying their version 1.5. Believe I will stay with this version and use it if I am not using Flock, my primary browser. Have a nice day. :)
-
I think it will be a major hit.
-
Hi Polonus,
Your link is redirecting to Firefox:3.0_PRD.
When is 2.0 due out?
I seem to have missed any problems with 1.5. I've heard that problems can be avoided by uninstalling all extensions before upgrading to 1.5.
EDIT: Looks like Firefox 2.0 Beta might be out soon:
http://www.mozilla.org/projects/firefox/roadmap.html
-
Hi FwF,
The development of FF 2.0 will be mainly to add new features for competitive reasons. It is mainly concerning the interface that will be renewed. The alpha version will not be the full beta-version due out coming April. The browser will have a better support for RSS-feeds, the bookmarks and history section will be fully redone. The browser will have a blacklist enabling Mozilla to block certain extentions from a central point for reasons of security or stability.
Protection against phishing sites and a possibility to save sessions. The first alpha release 2.0 will not have all these new features yet, these are for the 2.0 beta version due out coming April.
polonus
-
Does anyone know when the final version of Flock will be released?
-
...
Will it be another memory hog, will it crash while you try to scroll a loading page.
... ... ...
polonus
yup, firefox 1.5 = memory hog, but i don't find any crash problem...
i hope the memory management in 2.0 better than 1.5...
-
I believe the difference in memory usage in 1.5 is down to the speeding up of page loading when you use the Back/Forward icons. I don't mind so much I have a reasonable amount of RAM but it is currently at 115,380KB huge after being on all day.
It would be nice if there was an option to disable this function as it doesn't benefit me much I'm not flip flopping between pages.
-
There is, David:
http://kb.mozillazine.org/Browser.sessionhistory.max_total_viewers
I've heard that Firefox does cache these back-forward page views in each tab open, and will use a lot of free memory for the cache. The memory used depends on memory available: memory used in a system with 256M is less than a system with 2G. The really huge figures I've seen have been for systems with a lot of memory.
The memory leak issue is apparently different: this is when Firefox fails to return memory to the system after tabs are closed.
From what I've read, this may be due to certain Firefox extensions being present. A solution may be to uninstall extensions before upgrading, but I haven't seen anything definite yet.
For anybody hoping between pages in many open tags this memory usage will be a useful feature- as somebody said, it's not a problem unless your trying to play Quake4 at the same time.
-
Thanks for the link Frank, it will come in handy as I don't need that many pages stored in memory and I don't like to see any program running rampant with memory.
-
I must admit I'm still using Firefox 1.0.7.0 . I downloaded 1.5 when it was released , but haven't rushed to install it.
All my extensions work well, and (1.0.7.0) runs very well on my system . I have to admit to being reticent at upgrading to every new program release of any product. :-[
-
More on Firefox "leaks" here, real and not real:
http://www.squarefree.com/2006/02/04/memory-leak-progress/
To avoid any problems when upgrading, uninstall extensions beforehand; reintall after upgrading.
NB some extensions may cause memory leaks: NoScript is one.
Recognizing that memory leaks aren't always due to bugs in Firefox itself, Steve England and others have tested popular Firefox extensions for memory leaks. They found that Session saver, NoScript, IE Tab, and the combination of FlashGot and Filterset.G Updater cause leaks.
-
Hello FwF,
I have found that these memory problems are resolved when you
stealth browse from a memory stick. I have on my flash drive PortableFirefox (latest updates) with the following extensions NoScript, AdBlockPlus, SiteAdvisor, DrWeb anti-virus link checker, Adblock G updater, NukeAnything, Show IP & PwsHash installed, swift as it can be, no crashes, no crap on the host comp, no traces, no cookies, no history dat, no trace of a browser. Ideal when you do not want to leave a trace, but also for stability.
PocketFlock same story, alas no ported SiteAdvisor plug-in.
I write this posting from inside FF 1.501 en-US. NoScript memory hog, no no sweat whatsoever on a USB stick. For me and other forum folks, go alternate via the mem stick. No traces on the host computer, unless you are not going to them files there (pics etc, first take the also onto the mem-stick).
Safe, clean and fast,
polonus
PS Stealth browsing I learned from bob3160, the man with many a good idea.
-
PS Stealth browsing I learned from bob3160, the man with many a good idea.
Thanks for the compliment polonus but that's not how I browse.
For me the programs on a USB Drive are a convenient way to "Do it my way" on a strange computer when
I'm helping someone clean up their mess.
It's not my normal way of accessing the INTERNET or anything else for that matter.
For that I use my computer. ;D ;D
-
Hi forum members,
Some even try to go back, and make FF 1.5 work with all the old extensions, it can be modified to do so. Read here:
http://dancameron.org/general/903
polonus
-
Does anyone know when the final version of Flock will be released?
-
Hi Justin1278,
I know there is the pre-view update. The first public version was eventually planned February, but February gone, and March nearly ended, no sign of them going public. I hope it will not be abandoned, too good a project for that. It is all in the stars do far. Read here: http://www.foolswisdom.com/~lloyd/wordpress/index.php/flock-is-not-an-invite-beta/
So flock first will have kind of an alpha release.
polonus
-
I just got off of the telephone with "Colin" who is associated with "Flock". His name and phone number are listed at the Flock website. I asked him about the future of Flock. His answers to me are just about the same information that is at the URL that Polonus listed in his last post here. He just advised folks to be patient, understanding, and that we would be surprised and pleased with the "Robust" Flock that is coming out soon. This is all I can report to you from the phone conversation with Colin. :)
-
Hi Neal,
It seems that there is an awful lot of testing going on at the garage, where Flock is "cooked up". The testing is for Photobucket integration, bugs aside will give a new release.
polonus