Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Mozilla The Internet IT

Firefox 1.05 Released 85

Zebbie writes "The Mozilla Foundation released Firefox 1.05 today. The release notes indicate that there have been some 'security fixes' and 'improvements to stability.' From the web site: 'Firefox 1.0.5 is a security update that is part of our ongoing program to provide a safe Internet experience for our customers. We recommend that all users upgrade to this latest version.' It is interesting that these security updates are not yet posted on the security advisories page."
This discussion has been archived. No new comments can be posted.

Firefox 1.05 Released

Comments Filter:
  • Just checked the page, and they do seem to be listed now.
  • by sanmarcos ( 811477 ) on Tuesday July 12, 2005 @09:41PM (#13050021)
    Anybody experience the huge memory usage when opening a few big images?.

    Firefox should focus on improving the bookmark manager, the preferences, and polishing up the UI, but not forget about the most important things, speed and stability that is.

    It started as a lightweight mozilla, but it consumes just as a big chunk of memory as Mozilla does.

    Today, Firefox is the only serious competition to IE, (I see a lot of people using FF, even non geeks). Also, remember that another of Firefox key features is security. Lets hope that IE7s new features (that are similar to the ones FF always had, tabs, search box, etc), dont take away market share from FF.
    • Yes, I hope IE7 doesn't take back this market share, but really I don't know wtf microsoft was doing all this time. They could have easily released a version of IE with a hacked in tabbed browser and stop js popups by default. Even with the current security issues a lot would have probably stayed.

      It's not like your going to get them to switch with 'Look! It's open source and standards compliant!'
    • Firefox for Win32 is incredibly stable and fast, only crashing perhaps once every few weeks if not months, and usually only when using video plugins. Under Slackware Linux 9.1, Firefox has been sucking worse and worse ever since it was called Firebird 0.6, to the point now where it runs for LESS THAN ONE HOUR before slowing to a stop and sucking up 100% CPU, requiring a restart. This is not a Slackware problem - a friend of mine with an identical Slack 9.1 setup has never had any problems like this with Fir
      • My preference is still firefox way over IE. But the 100% CPU usage on so many websites is brutal on your hardware. You can't even leave your browsers open for a long period of time.

        • I've noticed that 100% cpu usage usually occurs when a page somewhere has a Flash rich-media ad running. With no way to "stop" flash from running on such a page, I've found that installing flash-block and/or ad-block fixes the problem.
        • I've found that it's mainly Flash that makes Firefox eat up the cpu. Try running flashblock and see if it clears up your issue.
      • by Slowping ( 63788 ) on Tuesday July 12, 2005 @11:18PM (#13050495) Homepage Journal
        Hmmm which firefox versions are you using?

        I have three computers (all Linux) which has firefox as their browser. Two desktops and one laptop. All three of them run cpufreqd.

        My two desktops stay up for months on end. Thanks to tabbed browsing, I leave just one browser window open and use it for everything. I've had firefox stay up for as long as the machine, without problem.

        For all three computers, I comfortably browse a various collection of websites, including many which have flash or java. None of the machines are taxed enough to force cpufreq into the gigahertz range.

        You sound like you know what you're doing, so I won't question the poor behaviour you're seeing. Maybe you're browsing multi-lingual websites? Multibyte fonts killing the browser? Maybe a bad plugin or extension? I'm not sure what the problem might be or what to suggest if you've already talked to the developers.
        • As I said, this has been with every version since Firebird 0.6, increasingly worse up to and including the new Deer Park alphas. I should also note that creating a new profile from scratch did result in one improvement -- now it generally crashes quickly instead of hanging on at death's door for days at a time sucking all my CPU. Of additional note is that this problem continues even when I do not have Flash installed, with ALL plugins and extensions disabled, AND with both Java and Javascript disabled. How
      • If you're using tabbrowser extensions, don't. I did for a long time and finally figured out that it was making firefox suck. I now use Sessionsaver and MiniT (to drag tabs around)
        • I installed an extension once (on Win32) that caused the firefox.exe executable to hand every time I closed the last browser window. As a result, Starting a new copy of Firefox seemed to have absolutely no effect.

          Moral: Try running Firefox in Safe Mode before you conclude something's wrong with the browser itself.

      • excuse the question, but what on earth are you doing still running Slackware 9.1? If the 2.4 kernel is under version 25, its probably either a horrible memory leaker, or has kernel security issues.

        Note I am not saying your firefox problem is directly related to the kernel. I still use mozilla on Slackware, and have not been experiencing the problems you claim to experience.
      • I've noticed that JavaScript enabled will cause Firefox to continously use 100% CPU and be unresponsive. One fix is to disable JavaScript and only enable it when needed. The culprit is ads served via JavaScript from kontera.com, so I just blackholed kontera.com.
      • First - Firefox is stable and works a dream, I would heartily recommend it, geeks read on:

        This is not a Slackware problem - a friend of mine with an identical Slack 9.1 setup has never had any problems like this with Firefox.

        If you can prove that Firefox works on your other friends Slackware, then as well as saying there is nor underlying fault with slackware, it also says there is no underlying fault with Firefox (in that equation).

        So the factor would seem to be your own system setup.

        I had some rough
      • Try creating a new user (or even just a new profile) and see if that helps. It might be someting in your user config that's breaking things.
    • The GTK2 version of Firefox consumes even more memory. Between xft/pango and increased load on the system's xserver, there's a lot going on and a lot of RAM and CPU being consumed.

      There's always the option of building a faster but slightly uglier GTK1 version, but then you start to get hung up on the performance limitations and RAM usage issues of the Gecko rendering engine itself.

      Mozilla/Firefox is slow, even today. Buy more RAM and a faster hardware, I guess.
    • Lets hope that IE7s new features (that are similar to the ones FF always had, tabs, search box, etc), dont take away market share from FF.

      Actually a new IE "feature" usually means a "new hole to exploit".

      So I am optimistic that FF will be able to continue to gain market share.
    • Also, remember that another of Firefox key features is security.

      A comparison of unpatched known vulnerabilities[1] in latest public version browsers (by securityfocus), ranks firefox as 8/9th:

      Browser: Number of known vulnerabilities

      1. Konqueror: 0
      2. Opera: 0
      3. Safari: 0
      4. Netscape Browser: 1
      5. Camino: 1
      6. OmniWeb: 1
      7. Internet Explorer for Mac: 1
      8. Mozilla: 2
      9. Mozilla Firefox: 2
      10. ...

      so although they are making security a priority, it looks like they're not a "key" leader.

      - p

      --

      1. Compariso [wikipedia.org]
      • so although they are making security a priority, it looks like they're not a "key" leader.

        Your inference that security focus listing several browsers with 0 known security holes makes them secure, is erroneous. I'm sure we'd see a flaw or two with some of the other browsers if they were enjoying the recent surge in popularity and attention that firefox is enjoying.

        Oh, and your reference URL shows firefox at 0 vulnerabilities now. And Safari now has 1.
        • Just like how the most popular web server (Apache) has way more vulnerabilities than the less-popular one (like IIS).

          Oh wait, it doesn't. So much for that theory.

          • Stop and read it again. Nowhere did my comment say that they would have move vulnerabilities than mozilla. It simply said that they would probably have more than 0.

            So much for reading comprehension.
    • Firefox has a long standing memory leak flaw. Is isn't the bext pr0n browser, since you shoudl restart is periodically.

      I wonder if they fixed css handling on 'save page as' (I doubt it) or if this release will break all my plugins and niceties. (they don't mention) :-(

      Firefox wins on security because of philosophy, that is, educate the user, and empower. Microsoft says use 'run executable' if they are signed.

      And activeX. And the fact that IE is still closer to the OS, and thus more of a hole.
    • Additionally, temporarily browser lockups when loading huge web pages. Its quite annoying when you have a couple of tabs open, because it effectively disables your browser until it has downloaded.
    • Comment removed based on user account deletion
  • by RzUpAnmsCwrds ( 262647 ) on Tuesday July 12, 2005 @11:29PM (#13050542)
    Has anyone else noticed how SLOW Firefox is on Linux?

    On Win32, on my Athlon 64 3200+ system, Firefox takes about a second and a half to render a 1000-comment Slashdot page (IE takes about half a second, interestingly - Trident seems to be very good with nested tables).

    On the same box, under Ubuntu Linux (and Fedora as well), Firefox takes over NINE SECONDS of 100% CPU to render the page. Konqueror, in comparison, takes under two seconds.

    What's wrong here? Why is Firefox on Windows nearly six times faster than it is on Linux?

    No one at the LUG seems to believe me until I *show them* the difference - and demonstrate it on *their* system to show that it's not a config problem.

    Try it yourself.
    • Yes, it seems Firefox is slower on Linux to me as well. I'm not sure why that might be. Perhaps Windows has a more consistent API? I really don't know, and though it usually doesn't take very long (i.e. most pages aren't so long as to require a lot of work) I do hope they fix that eventually.
    • Disable IPv6 (Score:4, Informative)

      by Rafikichi ( 831285 ) on Tuesday July 12, 2005 @11:54PM (#13050630)
      Goto about:config in Firefox. Set this string to true: network.dns.disableIPv6 I don't know why, but having IPv6 enabled slows down the broswer incredibly in Linux... but not on Windows. Turn it off and Firefox loads pages like the rest of 'em.
      • Re:Disable IPv6 (Score:4, Informative)

        by marcovje ( 205102 ) on Wednesday July 13, 2005 @01:54AM (#13051101)

        IIRC it has to do with DNS hosts that don't answer at all (or correctly) to IPV6 DNS requests. Some bad home routers also are said to be a possible cause

        (From https://bugzilla.mozilla.org/show_bug.cgi?id=68796 [mozilla.org])

        When IPv6 is enabled on the client machine, mozilla does a AAAA lookup first,
        and if there is none, does a lookup for the A record. Correct response for a
        name server if there is no AAAA record (but the domain exists) is to return
        NOERROR, with an empty reply. The BBC server returned NXDOMAIN (which was
        incorrect), and mozilla exhibited correct behaviour by assuming that the domain
        did not exist.

        See also
        https://bugzilla.mozilla.org/show_bug.cgi?id=23160 7 [mozilla.org]
      • To elaborate on this, the IPv6 thing isn't a problem in all distros, but it was (for me) in Ubuntu -- the first distro I've used where IPv6 was enabled by default. I disabled it and everything works better.

        Disabling it just in Firefox was good enough for the browser, until I got a local DNS running on the same system, at which point it reverted to the slow lookups, until I disabled IPv6 system-wide.
    • I use Win32 and Linux side by side every day, and have not noticed any speed difference between the two build targets. I regularly browse Slashdot and don't see render times like you're experiencing, and I am a fairly impatient guy when it comes to waiting for computers.

      I cannot speak of the difference between IE6 and FF since I so rarely run IE.

    • Firefox takes about a second and a half to render a 1000-comment Slashdot page

      Off-topic, I know, but you'll get my eternal respect and I'll mark you as an official ./ friend if you tell me how you manage to display 1000 comments on one single slashdot page.

      My user page says:
      Comment Limit (only display this many comments, for best results, set this to a low number and sort by score) If set above 100, then it is ignored and 50 is used instead.

      I just _hate_ the way ./ limits the number of comments o
      • I believe that the comment limit only applies to first-level comments, not replies. In articles with 1000+ comments, the number of replies at 4+ is substantial (I show everything 4+), so you can get a substantial number of comments on a page (in nested tables, none the less).

        It's not 1000 comments on one page, of course. But it is enough to fring FF on Linux to its knees.

        FF/Windows does OK, and, interestingly, Trident seems to chew threw nested tables.
  • by fluor2 ( 242824 ) on Wednesday July 13, 2005 @01:52AM (#13051095)
    1. Why do they still release just complete versions? I want an update to distribute to all our clients. Mozilla products are update hell.

    2. Why do they still insist on supporting many profiles per user? If I would like multiple profiles, then I would also create multiple users on my Windows.

    3. Why are profile paths so strange? The mozilla creates something like ...\Application Data\Mozilla\Firefox\Profiles\default.21a. That's hilarious.

    4. Why do they use Application data folder for cache? It's making the users' profile LARGE! They should use ...\Local Settings\ like internet explorer! (local settings belong to the machine, thus they do not roam like the application data folder)
    • 3 (weird paths) is IMHO mainly because of 2 (multiple profiles per user).

      I am not sure the purpose of 2... I'd call it a relic from userless systems like Win 9x, but in fact even that can be set up with (weakly separated) users; so I dunno. I've never used the feature myself.

      4. Perhaps allowing roaming (for bookmarks, etc.) is exactly why Application Data was chosen over Local Settings.
    • 1. Why do they still release just complete versions? I want an update to distribute to all our clients. Mozilla products are update hell.

      Scheduled to be fixed in Firefox 1.1

      2. Why do they still insist on supporting many profiles per user? If I would like multiple profiles, then I would also create multiple users on my Windows.

      Because it can be usefull to some people.

      3. Why are profile paths so strange? The mozilla creates something like ...\Application Data\Mozilla\Firefox\Profiles\default.21a

    • ... they're there to prevent a path-guessing attack like the ones used to fake out the security zones in Internet Explorer.
    • 2. Why do they still insist on supporting many profiles per user? If I would like multiple profiles, then I would also create multiple users on my Windows.

      You must be joking. How about instead I ask:

      Why does Windows insist on supporting multiple users? All I need is extra profiles in Firefox.

      Nobody stops you from using one profile if you like. I'm very happy on my system, which has one user (plus an administrative account) and multiple profiles (for myself and my wife, who likes a different set

  • Looks like the way the Javascript extensions for Chrome are integrated into Firefox are there in all the JS interpreter instances or contexts, they're just privileged. If the script is expected to be run from an untrusted environment, it's run at a lower privilege level.

    In an inherently safe model, the interpreter wouldn't contain any mechanism to request unsafe actions... they'd simply be syntax errors. They would only be added explicitly when the script was known to be running from a safe environment.

    Same with URI handlers: they would only be available from a reference within a safe environment.

    As I understand it, KHTML is an inherently safe design. Extensions have to be explicitly loaded into an instance of the HTML display object through I/O slaves. Gecko, apparently, isn't... at least not in a broser that uses Chrome for its user interface. It's better than the Microsoft HTML control, but it's not an inherently secure design as it sounded like originally.

    What are the options for a KHTML-based browser for Windows? On the Mac, of course, Safari is secure (so long as you turn off "open safe files after downloading"), but I haven't been following WIndows browsers that closely.
  • I like the idea of a light weight browser, but I thing that Mozilla should think about making tabbed browsing default. I see a lot of Opera users not changing to Firefox because of all the extensions needed.

    Tabbed browsing is the future in browsing, and Mozilla should think about that.
  • If anyone is looking for the zip'ed Windows version of 1.0.5, it's available here.

    http://ftp.mozilla.org/pub/mozilla.org/firefox/nig htly/2005-07-11-18-aviary1.0.1/ [mozilla.org]
  • They say both this,

    "Prior to installing Firefox 1.0.5, please ensure that the directory you've chosen to install into is clean and doesn't contain any previous Firefox installations."

    and this,

    "When upgrading, all your Extensions and Themes will be disabled. This is not an issue, but it may appear to be one (hence its listing here). For rationale, see "Extension and Themes" above."

    Surely that's a contradiction. If you install into a new directory then you aren't going to get your old extentions.

Don't tell me how hard you work. Tell me how much you get done. -- James J. Ling

Working...