Recommended Posts

Mozilla devs acknowledge that there might be some sort of problem. BUT, people always just bitch and bitch saying that Firefox is using too much memory...barely anyone runs the programs that would analyse the memory useage and all kinds of other technical stuff but these people never run the programs (which are small download and freeware btw) and send the report to mozilla. Its like the people are just making this crap up because I along with lots and lots of other never had/have a problem with memory useage. and the people that do bitch never send in these reports to help the devs out.

I don't use skins.

And why would that be the problem?

I have heard many reports that skinning it makes it slower in general. Lets hear it for inefficient programing.

Riddle me this, how much memory for firefox take up if we were still in the days of 1024 k memory?

Kindly report the OS you are using as well. No memory problems here using Gentoo Linux, but every Windows box I have ever used it on experiences this.

585071817[/snapback]

yeah, that's why I don't biatch about it too much - 'cause I know that widows it self doesn't handle memory in the best way.

But anyhow, I've got 512mb of RAM(soon 1GB), and when I use apps likes Paint Shop Pro, Flash MX or Visual Basic (that take a a LOT of memory) - I'm not on the web. It's work or play -not both :p

Mozilla devs acknowledge that there might be some sort of problem. BUT, people always just bitch and bitch saying that Firefox is using too much memory...barely anyone runs the programs that would analyse the memory useage and all kinds of other technical stuff but these people never run the programs (which are small download and freeware btw) and send the report to mozilla. Its like the people are just making this crap up because I along with lots and lots of other never had/have a problem with memory useage. and the people that do bitch never send in these reports to help the devs out.

585071811[/snapback]

fan.jpgbartsimpson.jpg

? i guess your meaning something about crap hitting the fan?

I for one am one that could help with the memory issues but no one ever submits enough info for us to be able to figure out what is causing the leakage. Ok memory leaks or is hogged on your PC, not everyones, so each instance is seperate because its not like everyone is expirencing the same issue caused by the same thing.

I do know that some of the memory hogging is caused by images not being unloaded from the cache. though and that is being worked on.

I've had FF take up to 300 megs of memory. This was with no more than 10 tabs open. Usually it's between 50 and 120 megs for me, but occaissonally it gets to ridiculous amounts such as this.

Also, 1.0 is the least stable build I've used, on my system.

you probably had a bunch tabs open that had lots of graphics. unstable? its the stablest build ever. Try a clean install and new profile. The older profiles with tweaks and such caused some problems which cause firefox to lag and crash from old extensions that left footprints in the profile.

I have been using Firefox since its conception and only had memory issue back then. Never had any issues after at least phoenix 0.5 and I have always extensively smoketested Firefox, phoenix and firebird. So you probably have some hack on your OS that screws up the memory management or you changed some setting in Firefox that you shouldn't of.

heres what i've noticed about mem useage ;)

mine generally runs at 10 - 30mb with one tab open this depends on how many pages i've loaded on that one tab add another tab and it will increase by about 7mb every tab after that seems to take about 1mb.

viewing flash content esspecially flash content with embedded FLV's will take up lots of memory (this is detailed on macromedias site and various other flash related sites FLV's are held in memory.

Other plugins/extensions also take ram i'm currently using a VRML plugin and that grabs 20mb when it loads and however much else it needs for the scene. To be honest though its not big deal minimise then maximise and it uses less (for some reason)

If your really bothered why use it? or failing that increase your page file buy more ram (i know buying more ram isn't always an option for everyone)

Really though memory useage is never something that can be exactly measured it all depends on what the system is up to at a given time its generally adviserable to stop some of the system services you never use always frees up memory and closes threads.

my firefox mem usage is 33mb atm and rising (btw minimising does drop the mem usage quite a bit)

if someone wants to reccomend a tool for analising the mem usage and tells me the best way to about it id happily submit the data to the mozilla devs to look into :)

offtopic

why is it auto update cant update my firefox to the latest version for me :( seems a bit pointless if it never downlaods program updates when they are avaliable

you probably had a bunch tabs open that had lots of graphics. unstable? its the stablest build ever. Try a clean install and new profile. The older profiles  with tweaks and such caused some problems which cause firefox to lag and crash from old extensions that left footprints in the profile.

585072299[/snapback]

No, they were all average pages, like xangas, forums and so forth. I don't even know of any graphic intensive sites I visit on a regular basis anyways. Also, it was around 10 tabs max when that happened, anymore open than that and FF tends to crash on me.

When 1.0 was released I did a completely fresh install. Deleted profile etc. Still, I get at least a crash a day and it's sluggish as hell for me. If I'm at a page with say, some thumbnails of photos from a party, and I click 5 or so at once to open in tabs, the browser is rendered unusable for 10-20 seconds more often than not, because it's sitting there loading.

I've had many times where FF simply freezes and the only thing to kill it is end process in taskman. I even had onetime I was using it where it just terminated itself out of no where with no warning.

Often when I'm typing somehting, like this reply, FF will go back for no reason. I won't accidently hit a hotkey or click a mouse button...it just goes back for no reason.

All this happens to me and I'm quite positive I'm free of viruses, spyware and the like. All using a clean install of 1.0, completely updated on a machine with over a gb of ram etc.

yes please do Raum so things like that can be worked out. Actually I basically have the crashing problem on a computer at college. Computers are all set up exactly the same, all are using the same user.js file and same settings for everything, same theme, and same extensions and yet only one computer always has problems. I'm completly confused on why it does and even after repeadted fresh clean installs the same thing.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • A 13 billion year old secret about our Universe's origin was revealed by Sayan Sen Image by Pascal Küffer via Pexels Researchers at the Max-Planck-Institut für Kernphysik (MPIK) in Heidelberg had recreated a key chemical reaction from the early universe, producing results that could change scientists' understanding of how the first stars formed. The study focused on the helium hydride ion (HeH⁺), which is widely regarded as the first molecule to form in the universe. Scientists believe HeH⁺ appeared around 380,000 years after the Big Bang, when the universe had cooled enough for electrons and atomic nuclei to combine into neutral atoms in a period known as recombination. This marked the beginning of chemistry in the cosmos. Immediately after the Big Bang about 13.8 billion years ago, the universe was extremely hot and dense. As it expanded and cooled, hydrogen and helium became the dominant elements. Once neutral helium atoms formed, they could react with ionised hydrogen nuclei, or protons, to create helium hydride ions. Although simple in structure, HeH⁺ played an important role in the young universe. It was the first step in a chain of reactions that eventually produced molecular hydrogen (H₂), a molecule made up of two hydrogen atoms and now the most abundant molecule in the universe. Molecular hydrogen later became a key ingredient in the formation of the first stars. At the time, the universe had entered a phase often called the cosmological "dark age." Matter had become transparent to light following recombination, but there were still no stars or galaxies producing visible light. Several hundred million years would pass before the first stars appeared. For those first stars to form, large clouds of gas had to collapse under their own gravity. To do that, the gas needed to cool by releasing energy. While hydrogen atoms can help with this process at high temperatures, they become less effective below about 10,000 degrees Celsius. Molecules can continue the cooling process by releasing energy through rotational and vibrational motions. Scientists have long considered HeH⁺ a potentially important coolant because of its comparatively large dipole moment, a property that describes how electric charge is distributed within a molecule and allows it to release energy efficiently. The amount of helium hydride present in the early universe may therefore have influenced how easily the first stars could form. At the same time, HeH⁺ was constantly being destroyed. Under primordial conditions, its main destruction mechanisms were recombination with free electrons and chemical reactions with hydrogen atoms. These reactions ultimately helped produce molecular hydrogen, linking the formation and destruction of HeH⁺ to the chemistry that shaped the early universe. For many years, theoretical studies suggested that reactions between HeH⁺ and hydrogen atoms would become much slower at low temperatures. Scientists believed there was an energy barrier along the reaction pathway that reduced the chances of the reaction taking place in the cold conditions of the early universe. The new study suggests otherwise. To investigate the process, researchers recreated a closely related reaction using deuterium, a naturally occurring isotope of hydrogen that contains one proton and one neutron in its nucleus. When HeH⁺ collides with deuterium, it forms an HD⁺ ion and a neutral helium atom. This allows scientists to study the reaction in a controlled way while closely mimicking the behaviour of the original reaction involving hydrogen. The experiments were carried out at the Cryogenic Storage Ring (CSR) at MPIK, a specialised facility designed to recreate conditions similar to those found in space. Researchers stored HeH⁺ ions in the 35-metre storage ring for up to 60 seconds at temperatures just a few kelvins above absolute zero and merged them with a beam of neutral deuterium atoms. By adjusting the speeds of the two particle beams, the team measured how the reaction rate changed with collision energy, which is directly related to temperature. The researchers found that the reaction rate remains almost constant as temperatures decrease. In other words, the reaction does not slow down at low temperatures as earlier models predicted. “Previous theories predicted a significant decrease in the reaction probability at low temperatures, but we were unable to verify this in either the experiment or new theoretical calculations by our colleagues,” explained Dr Holger Kreckel of MPIK. “The reactions of HeH⁺ with neutral hydrogen and deuterium therefore appear to have been far more important for chemistry in the early universe than previously assumed,” he continued. According to the researchers, the reaction appears to be barrierless, meaning there is no energy obstacle preventing it from taking place efficiently even at very low temperatures. The findings support recent theoretical work led by physicist Yohann Scribano, whose group identified an error in a widely used potential energy surface, a mathematical model used to describe how the energy of a system changes during a chemical reaction. The error appears to have caused previous studies to significantly underestimate reaction rates under primordial conditions. The new calculations closely match the experimental results. Together, they suggest that helium chemistry in the early universe may need to be re-evaluated. Because molecules such as HeH⁺ and molecular hydrogen played an important role in cooling primordial gas clouds, the findings could help scientists build more accurate models of how the first stars formed. By showing that helium hydride was likely destroyed more efficiently than previously thought, the study offers new insight into the chemical processes that shaped the universe during its earliest stages and helped set the conditions for the emergence of the first stars. Source: Max-Planck Institute, EDP Sciences This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • "What an interesting smell you've discovered"
    • It could EASILY be 70 for the base game BUT + lots of FOMO to make it up to 100-120, like a few days Early Access, online money, pre-order bonus cars, weapons, missions, clothing, avatars or profile stuff, etc... And still WAY TOO MANY people would buy those and make Rockstar insane money.
    • Just to understand: your solution to getting rid of an online password manager is...another online password manager?
    • Cjam 2.5.0.0 by Razvan Serea Cjam is a lightweight and fast MP3 editor for Windows that lets you cut, join, and edit MP3 files without re-encoding. This means your audio quality remains untouched, and edits happen instantly. Cjam is ideal for quick, lossless edits—whether you're trimming music, combining tracks, or preparing audio for learning tools or podcasts. It features batch processing, scripting support, cue and playlist file handling, and a simple interface. Cjam is perfect for anyone who needs efficient MP3 editing without the complexity of full audio suites. Cjam requires a PC running Windows 10 or later and Microsoft .NET 6.0 or later. Key features for Cjam: No Re-encoding: Edit MP3 files without losing quality. Cut and Join MP3: Easily cut, trim, and combine MP3 tracks. Batch Processing: Edit multiple files at once for faster workflows. Scriptable Interface: Automate tasks with a custom command language. Cue and Playlist Support: Handle CUE and playlist files for seamless audio management. Fast and Lightweight: Quick processing with minimal system resources. Lossless Audio Editing: Ensure your edits don't affect audio quality. Simple User Interface: Clean, intuitive design for easy navigation. File Format Support: Works with MP3, Cjam-specific file formats (CJAMC, CJAMJ, CJAM). Cjam 2.5.0.0 changelog: Added clipboard-based import/export support for mp3DirectCut Added clipboard-based export support for REAPER Added support for naming IMP3 elements Changed the Reset behavior to preserve Undo/Redo history; use Shift key + Reset button to clear it Added a new command parameter (qcp) Added 8 new entries to lang.txt (main_c124-126, main_d150-151, main_m082, vme_c014, vme_d005) Fixed a bug where the il parameter was incorrectly applied when pasting VMP3s into the main list Fixed several other minor bugs Download: Cjam 2.5.0.0 | 1.4 MB (Freeware) Links: Cjam Home Page | Cjam Manual | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Dedicated
      JuvenileDelinquent earned a badge
      Dedicated
    • First Post
      DrWankel earned a badge
      First Post
    • Reacting Well
      DrWankel earned a badge
      Reacting Well
    • Week One Done
      Supreme Spray LV earned a badge
      Week One Done
    • Week One Done
      Genuinetonerink- Dubai earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      504
    2. 2
      +Edouard
      163
    3. 3
      PsYcHoKiLLa
      91
    4. 4
      Steven P.
      75
    5. 5
      Michael Scrip
      72
  • Tell a friend

    Love Neowin? Tell a friend!