Why are Firefox programmers making it a memory eater?

  • Thread starter Thread starter Pengwuino
  • Start date Start date
  • Tags Tags
    Firefox Memory
AI Thread Summary
Firefox is reported to consume excessive memory, with instances of it using around 600MB while running multiple tabs and applications. Users express frustration over this memory usage, comparing it unfavorably to PC games that require less memory. Some suggest that Firefox's design prioritizes speed by utilizing available RAM, assuming users have sufficient memory on modern systems. However, this can lead to crashes, particularly when multiple tabs are open or when certain add-ons are active. To mitigate memory issues, users recommend disabling non-essential add-ons and tweaking Firefox's settings. Alternatives like Google Chrome and Opera are suggested for their lower memory overhead. Users also discuss the frequency of crashes, with some attributing them to specific add-ons or system configurations. Overall, while Firefox is favored for its customization and flexibility, its memory consumption remains a significant concern for many users.
  • #51
I think everyone here needs to understand that programmers occasionally miss the Balmer peak. It's an honest mistake, but it does happen.
 
Computer science news on Phys.org
  • #52
Ok I give up. I tried to search it out, but to no avail.
What is Ballmer Peak?
 
  • #53
Pattonias said:
Ok I give up. I tried to search it out, but to no avail.
What is Ballmer Peak?

Lol I think it means that programmers code better and do things previously impossible when they code drunk/high.
 
Back
Top