What is Digg?116 Comments
- tom6a, on 10/12/2007, -3/+109Of course, if you had used Firefox 2.0 Beta to write the post you would have a built in spell check!
- wayjer, on 10/12/2007, -6/+70Sorry about spelling, should be Tomorrow, cant edit it now.
- eihcirdivad, on 10/12/2007, -5/+32whenever i have to spell tomorrow i say in my head tom - or - row. works well for me.
- Nukem945, on 10/12/2007, -2/+26Can't wait for session restore and undo close!! I use the session manager extension at work, but for some reason, it makes firefox unresponsive sometimes. The only solution I am left with is to load firefox safe mode and reset all settings.
I love how the really popular and useful extensions are eventually integrated into the newly released builds. - jole, on 10/12/2007, -13/+37To be honest I can never spell "tomorrow" correctly either.
- inactive, on 10/12/2007, -1/+19It would certainly be a privacy issue ... I can't think of anything more embarrassing then having someone come up to you when you're browsing something questionable, you shut the browser and then they want to show you some site hah.
- Kiyomizu, on 10/12/2007, -2/+15Firefox 2.0 Beta release has been postponed until later this week. People will have to wait just a little longer to start using it.
http://www.linuxinsider.com/story/9gyK6AfPCk43eS/Firefox-20-Official-Beta-Release-Postponed.xhtml - inactive, on 10/12/2007, -0/+12Agreed. Just middle-click the tab you want to close...
- digix, on 10/12/2007, -3/+15"Hmm... Silly question: wouldn't session restore be a security issue?"
The session restore that I have used in the past will attempt to return to the page, but the cookies are gone. If it was a site that would need credentials, then you are prompted for them again.
I can see where you are coming from, but I have not seen any security issues thus far with session restore extensions. - inactive, on 10/12/2007, -9/+21The caching of tabs (I'm guessing that's what you're referring to) is only one of the memory issues.
After 4 years the FF developers clearly don't give much thought to memory usage, stability and speed, because the users obviously don't care. The majority anyway. People who are above the "it's open source ***** microsoft" mentality and actually care about the performance of their workstations and software long since switched to Opera and/or even IE.
Instead of modding me down prove me wrong. Gazillions of people have complained about these issues since very early versions. It has been consistently ignored by the "quality" assurance guy (Asa "what's my job again? Oh yeah, writing how much IE, Opera and everyone who's not me sucks" Dotzler) and programmers alike. - dave98, on 10/12/2007, -2/+13 1. Start Firefox.
2. In the Address Bar type “about:config” and press Enter.
3. Right-Click and select New->Integer.
4. A box requesting the Preference Name will popup and you should enter “browser.tabs.closeButtons” (without the quotes). Press OK to continue.
5. Now you need to select the type of close button you want: 0 - display a close button on the active tab only, 1 - display close buttons on all tabs, 2 - don’t display any close buttons, and 3 - display a single close button at the end of the tab strip (Firefox 1.x behavior). After entering the value corresponding to your preference press OK again. - Sheco, on 10/12/2007, -3/+13cogen: You misspelled chick you n00b LOL ROFL LMAO!!!1 pwned!!!one!
- YourTechSupport, on 10/12/2007, -10/+20Built in? WOOT!!
- ahawks, on 10/12/2007, -1/+11There have been plenty of articles explaining that what _most_ people think is Firefox's memory leakage is just caching of pages for history & stuff. However, there is a NASTY memory leak in the Flash plugin.
I had a fresh browser instance, and went to Newgrounds to play a game. I left the game paused and went to work. When I came home, firefox was taking 420mb of ram, with just that one window open. - Xoligy, on 10/12/2007, -2/+12"Yes, my tongue is planted firmly in my cheeck"
Oh the irony. - SteveMax, on 10/12/2007, -3/+12@r2d7
You have a point. Most Firefox users don't really care that much for their browser's quality. The community-driven Seamonkey (and even the Mac-only Camino) are much better in every aspect; but they're not "cool". If you open Seamonkey with 10 tabs, IMAP mail and composer, it still uses less memory than Firefox with 2 tabs and a couple of minutes of usage, but people still say that "seamonkey is resource-heavy and slow, while FF is clean, light and fast".
The Gecko core started suffering since it moved from being based on the suite to being driven by FF+TB. The FF developers have a very closed view, don't usually take advices and really believe themselves to be open-source gods. I'm seriously considering non-Gecko browsers for the future, as Mozilla is turning into the monster it was set to fight (namely, the Navigator+IE pieces of crap). - Mekun, on 10/12/2007, -6/+14Hows is firefox 2.0 working with the acid test?
Stopped using IE about a year ago. Firefox is so much better at handling popups and tabs is a must. I just hope they fix the amount of memory it hogs. - vize, on 10/12/2007, -1/+9It is a RC for a beta
- lonerangerusa, on 10/12/2007, -6/+13I agree with Mekun, ive been using firefox for a few years, and it takes up lots of memory
- Urusai, on 10/12/2007, -2/+9I'm holding out for RC2. Only early adopters would download a RC1.
- x713, on 10/12/2007, -0/+7Not much to have in the screenshots... just better spelling in them.
- archer75, on 10/12/2007, -2/+9improvements include a close button on all tabs? That's why I don't use another browser. I hate the close button on the tabs.
- dave98, on 10/12/2007, -8/+15it probably doesn't matter much now but...
both those features have existed for a while now in the Tabmix Plus extension and its much more refined and stable than the sessionsaver extension
https://addons.mozilla.org/firefox/1122/ - jbrackett, on 10/12/2007, -2/+8Firefox Memory Usage FQA:
http://plugindoc.mozdev.org/faqs/memusage.html
Leak Monitor Extension:
http://dbaron.org/mozilla/leak-monitor/
Reducing Memory usage article:
http://kb.mozillazine.org/Reducing_memory_usage_-_Firefox
Weblog article from developer asking for memory leak bugs to be filed and howto:
http://dbaron.org/log/2006-01#e20060110a
More reading from developers:
http://www.squarefree.com/2006/01/13/memory-leak-detection-tool/
http://weblogs.mozillazine.org/ben/archives/009749.html
http://weblogs.mozillazine.org/ben/archives/009774.html
I fail to see where people get off saying that memory leakage isn't being addressed. - jbrackett, on 10/12/2007, -1/+7I hope my responses don't peg me as a firefox evangelizer. I actually do web development so I use several browsers semi-regularly. The only browsers I really don't like are IE6 and below...
resolved memory leak bugs on the branch (2.0):
* Bug 168411 - Move bookmarks transactions into a JS service (adding a bookmark leaks the Add Bookmark dialog)
* Bug 206520 - XMLHttpRequest leaks memory if send() not called and event listeners set
* Bug 283565 - Improper use of Realloc (mlk/crash) and silly return value for OOM
* Bug 289689 - Memory leak: nsDebugImpl::Assertion, Create Process
* Bug 289897 - huge memory leak when klipper is running
* Bug 316775 - leak when selecting
* Bug 317478 - leaks due to global scope polluter being removed from not enough (?) prototype chains
* Bug 319980 - javascript garbage collector not run when supposed to, leading to "memory leak"
* Bug 323454 - [FIX]Don't leak the channel and XMLHttpRequest object if AsyncOpen fails
* Bug 321283 - Using Find causes documents to leak
* Bug 323532 - Leak when using history autocomplete
* Bug 323377 - Lots of leaks in nsInternetSearchService
* Bug 325984 - DOMWindow leak with
* Bug 330624 - accessibility code (when accessibility enabled) holds on to DOM nodes until shutdown
* Bug 330780 - [ATK only] global nsAppRootAccessible is not released on shutdown
* Bug 330878 - Firefox leaks the update.xml document when it checks for updates
* Bug 333134 - Accessibility still leaking when AT used
* Bug 333764 - Livemark Service leaking nsRDFResource and RDFServiceImpl references
* Bug 334105 - [FIX]ASSERTION: Bogus: '!mHead' (nsLineBox.cpp#916 - nsFloatCacheFreeList::Append)
* Bug 336922 - nsAnnotationService leaks
* Bug 337044 - Search engine Manager leaks an observer when canceled
* Bug 341301 - 1.8 branch firefox leaks like a sieve
resolved memory leak bugs on the Trunk (3.0):
* Bug 168411 - Move bookmarks transactions into a JS service (adding a bookmark leaks the Add Bookmark dialog)
* Bug 206520 - XMLHttpRequest leaks memory if send() not called and event listeners set
* Bug 241518 - calling addEventListener with a closure holding a content node leaks the document
* Bug 283565 - Improper use of Realloc (mlk/crash) and silly return value for OOM
* Bug 289689 - Memory leak: nsDebugImpl::Assertion, Create Process
* Bug 289897 - huge memory leak when klipper is running
* Bug 315708 - Should release found link and current window object from nsTypeAheadFind.cpp
* Bug 315951 - unknown content type dialog leaks domwindow
* Bug 316775 - leak when selecting
* Bug 317478 - leaks due to global scope polluter being removed from not enough (?) prototype chains
* Bug 319980 - javascript garbage collector not run when supposed to, leading to "memory leak"
* Bug 320211 - parser-related leak when loading DOM inspector in Firefox
* Bug 321040 - observer service should remove null weak references from observer lists when enumerating
* Bug 321283 - using Find causes documents to leak
* Bug 323377 - Lots of leaks in nsInternetSearchService
* Bug 323441 - Memory leak if a site sets location and then document.writes (e.g. when visiting www.economist.com)
* Bug 323454 - [FIX]Don't leak the channel and XMLHttpRequest object if AsyncOpen fails
* Bug 323532 - [FIX] Leak when using history autocomplete
* Bug 323534 - createTreeWalker can cause leaks due to cycles created by closures
* Bug 325305 - minor memory leak in CERT_FindCertByNameString
* Bug 325984 - DOMWindow leak with
* Bug 326491 - Leaked observer service leaks things on shutdown
* Bug 327670 - Memory leak in MarkOutOfFlowChild
* Bug 329071 - Leaking an nsZipFind if jar enumerator allocation fails
* Bug 330624 - accessibility code (when accessibility enabled) holds on to DOM nodes until shutdown
* Bug 330649 - leak nsContentShellInfo objects
* Bug 330780 - [ATK only] global nsAppRootAccessible is not released on shutdown
* Bug 330878 - Firefox leaks the update.xml document when it checks for updates
* Bug 331706 - Leak when scrolling
* Bug 333134 - Accessibility still leaking when AT used
* Bug 333296 - nsCharsetConverterManager::GetList leaks array if it can't get catman
* Bug 333298 - nsTextToSubURI::UnEscapeAndConvert leaks pBuf if decoder->Convert fails
* Bug 333313 - oom mlk in InternetSearchDataSource::BeginSearchRequest
* Bug 333354 - mlk on early return
* Bug 333672 - Leaking imgSurf in nsCanvasRenderingContext2D::DrawImage
* Bug 333674 - We leak oldVal on OOM in nsUint32ToContentHashEntry::PutContent
* Bug 333733 - Could leak attr in nsFrameUtil::Tag::ReadAttrs
* Bug 333764 - Livemark Service leaking nsRDFResource and RDFServiceImpl references
* Bug 333796 - Could potentially leak ctx in nsSVGCairoGlyphGeometry::GetBoundingBox
* Bug 334105 - [FIX]ASSERTION: Bogus: '!mHead' (nsLineBox.cpp#916 - nsFloatCacheFreeList::Append)
* Bug 334421 - Shutdown leak of mEvictionQ entries
* Bug 334898 - jsj_ResolveExplicitMethod leaks arg_start if convert_java_method_arg_signatures_to_hr_strin fails
* Bug 335785 - wrapper reparenting leak on gmail
* Bug 336475 - Coverity NSC_VerifyInit error paths don't free "info"
* Bug 336477 - Coverity CERT_UncacheCRL variable named "returned" is not freed if !removed
* Bug 336922 - nsAnnotationService leaks
* Bug 336961 - DOM Inspector leaks (dom.js)
* Bug 337029 - [mlk] bookmark properties dialog leaks a microsummaryObserver when canceled
* Bug 337044 - Search engine Manager leaks an observer when canceled
* Bug 337110 - Coverity OOM Crash and memory leak [@ PK11_CreatePBEParams]
* Bug 338003 - imgCache::Init leaks imgCache if do_GetService fails
* Bug 338075 - CID 538, RESOURCE_LEAK
* Bug 339477 - tabbrowser.xml's observer destructor never gets called, leaking mTabClipWidth at shutdown
* Bug 339913 - Coverity OOM leak in sec_asn1d_add_to_subitems
* Bug 339914 - Coverity leak in NSS_CMSEncoder_Start error paths
* Bug 339916 - Coverity 464, leak after OOM in CERT_DistNamesFromNicknames
* Bug 339919 - Coverity 905, leak in CERT_GetCertNicknames
btw this could be found in my first link above - ascott9, on 10/12/2007, -0/+6I really really want to know why they haven't addressed the memory issue. It seems like its the main bug that everyone holds against them. Have they addressed and I just don't see it on the roadmap/bugzilla? Anyone who follows the firefox development care to chime in?
- inactive, on 10/12/2007, -0/+6I don't think I've ever used the close button on tabs. Control + W is used widely to close tabs. I use it in Firefox, Photoshop, and text editors. Works like a charm.
- TomP, on 10/12/2007, -2/+8dave98: Great I've gotta do that every time i install ffx now :(
- cell00, on 10/12/2007, -2/+7It asks if you want to restore what you had before. So you can just press no.
- snipes, on 10/12/2007, -1/+6Am I the only one that hasn't seen any screenshots?
- inactive, on 10/12/2007, -1/+6Wait, how can it be both a beta and a release candidate at the same time? A beta is usually unstable and not yet complete, while an RC is supposed to be the final version, unless serious bugs or flaws are found during the RC stage.
Unless this is an RC for the beta :) - cogen, on 10/12/2007, -5/+10lol, spelchek iz 4 n00bz!
(Yes, my tongue is planted firmly in my cheeck.) - conorryan, on 10/12/2007, -0/+5This was posted on the Mozilla Developer Center
"Firefox Beta 1 Code Freeze Tonight at 11:59 PDT!
Howdy Everyone,
Friendly reminder that tonight is the code freeze for FF2 Beta 1 in preparation for a release next week. We are tracking the list of critical b1 bugs here.
We need everyone’s help in producing patches, doing reviews, and verifying bugs. If you have anything on the blocker list - or are asked for comment and review please help out as fast as you can.
We’ve also added the triage queries to the 1.8 tinderbox pages to make it easier for everyone to keep track of the critical bugs. If you can help out with anything on the blocking lists please do!"
I can't wait! - pile0nades, on 10/12/2007, -2/+7@r2d7
That's why you don't close the browser, but just close the tab with the pr0n in it. - dykesat, on 10/12/2007, -1/+6FF 1.0 RC1 turned out to be the actual release build.
- supernovus, on 10/12/2007, -1/+6Maybe it's for the vast majority of people on the internet who cannot spell worth a damn. I know a lot of people in the 16-35 demographic who couldn't spell arrogant properly, but may be able to spell prick. What this says for the education system is another story altogether. When I see a high school graduate who can't spell "propurly" (sic) it makes me wonder what we are teaching these kids in school.
Plus I doubt that the kids who post stuff like "lol dats so kewl XD" would want a built in spell checker, it might mess up their "unique" writing style. - XistenZ, on 10/12/2007, -2/+6TMP has the option of asking if you want to restore the last session or not when you start up a new firefox session. It is just a setting, and if you know any previous session was inappropriate you can always choose no.
- dave98, on 10/12/2007, -2/+6Yes the memory problems can be a pain for some although personally it hasn't been as bad as some people have experienced
however, for those who are looking for a bandaid solution, theres the 'restart tabbed' extension that restarts firefox with all your current tabs intact.
https://addons.mozilla.org/firefox/2347/ - br0ther, on 10/12/2007, -2/+6try using camino instead.
- antoniojvr, on 10/12/2007, -7/+11Ahh they're using the Microsoft tactic. Brilliant!
- dave98, on 10/12/2007, -0/+4Most extensions should work fine with just a simple maxVersion change.. Adblock Plus should be no different.
MrTech Local Install or Nightly tester tools will help automate that process for you http://www.mrtech.com/extensions/local_install/ - chrisgeleven, on 10/12/2007, -0/+4Beta 1 doesn't have much in terms of UI changes, except that the search box got some tweaking, spellchecking (just a dotted red line underneath misspelled words), and the close buttons on each tabs.
Beta 2 is supposedly going to have a "visual refresh" of the interface. That is when screenshots are going to show something meaningful. - TomP, on 10/12/2007, -0/+4I think I like 1.5 tabs better... and when i search for something and hit enter it doesn't work so i have to click it with mouse!
- Jugalator, on 10/12/2007, -1/+4I doubt it, as the plan was laid out months ago.
- zoltanthebold, on 10/12/2007, -2/+5Those are some interesting points raised. It's interesting to note that Firefox usage and evangalisation is every bit as biased as the community/company they set out to tackle.
Although the $30 million they make each year no doubt has dulled their fervour to take on the Redmond giant. - TokenUser, on 10/12/2007, -2/+5Spell checking is also great for fat fingerred typists.
But - whats this? Building something INTO FF? Isn't that what the holiest of holies - the "extension" - is for?? - rodtrent, on 10/12/2007, -1/+3Firefox releases are like Microsoft Patch Days for IT folks. Trying to stop installations of unnaproved software is an IT person's full time job.
- hollywoodone, on 10/12/2007, -1/+31. Spell check works good.
2. Allows the disable of extensions instead reinstalling (better than firebox safe mode because you can select which ones)
3. All my extensions works great, DTA, CustomizeGoogle, and Siteadvisor.
4. Recently closed tabs is nifty. - stomicron, on 10/12/2007, -2/+4....and there's your token Microsoft comment.
Thanks for the update, Kiyomizu - djoek, on 10/12/2007, -0/+2http://digg.com/software/Firefox_2.0_beta_1_is_HERE!!
nuff said -
Show 51 - 100 of 114 discussions
Digg is coming to a city (and computer) near you! Check out all the details on our 
© Digg Inc. 2009
— Content created and posted by Digg users is