Firefox 1.0 has major memory leaks

By vcv
in Web Browser Discussion & Support

 Share

Recommended Posts

Mentor

vcv

Posted
Posted

This is NOT an attempt to troll by any means, it is meant as a warning.

I ran a memory profiler on Firefox 1.0 just now, and the results were astonishing. The tool used detects any memory that a program does not free when it is done with that memory. These leaks are leaks found after the program was done.

2 tabs were loaded, and each page reloaded twice. Firefox was only running for about 60-90 seconds.

Just to make sure I was reading it right, I ran the profiler on 4 other applications, 2 other web browsers, an a chat program and an email client. All other programs reported fewer than 10 memory leaks.

GlowCode Leaks -- C:\Program Files\Mozilla Firefox\firefox.exe, Tue Feb 22 07:55:22 2005

Leaks found, 6416 blocks, 242150 bytes

Click here for the full results.

Link to comment
https://www.neowin.net/forum/topic/288645-firefox-10-has-major-memory-leaks/
Share on other sites
Grand Master

Steffan

Posted
Posted

That's nothing new about firefox. If you do a search on neowin, I bet you will find other posts about the memory leak. This is just the first version of this browser. Give it some time before you complain about the memory leak.

Grand Master

The_Decryptor Veteran

Posted
  • Veteran
Posted

well, if you didnt close the program, and that stayed there, then it's not a leak

it's a leak if the memory isnt freed, so if you close that other tab, the memory usage doesnt go down.

But yeah, there is a slight problem with firefox's memory, you can change a option to make it use a max of 16MB a tab, it's in about:config, called cache something.

Mentor

vcv

Posted
  • Author
Posted
That's nothing new about firefox.? If you do a search on neowin, I bet you will find other posts about the memory leak.? This is just the first version of this browser.? Give it some time before you complain about the memory leak.

585515088[/snapback]

What a joke. This is na/b> leak, this is thousands of leaks.

First version of the browser, so thousands of memory leaks are ok? Please spare me the BS. Memory leaks are NEVER okay. There is an acceptable range, but 6,000 is NOT an acceptable range, nor is 14,000.

Making sure memory is properly managed should be a TOP PRIORITY for any software.

well, if you didnt close the program, and that stayed there, then it's not a leak

it's a leak if the memory isnt freed, so if you close that other tab, the memory usage doesnt go down.

But yeah, there is a slight problem with firefox's memory, you can change a option to make it use a max of 16MB a tab, it's in about:config, called cache something.[/quoPLEASE READ WHAT I ALREADY SAID./b>

1. This was the report fafter the application had been closed/i>

2. This is memory thwas not freed when it should have been/i>

3. I only loaded 2 tabs, and refreshed each page twice. This should not cause such harsh memory problems.

Grand Master

supernova_00

Posted
Posted

most of those apparent leaks are from mostly from the same place....anywho I submited your info so that people that better understand all that mumbojumbo and decipher it.

woah just seen you said this was after you closed the program!? something is wrong with your profile then becuase Firefox does not keep memory after it's closed

Rising Star

lhnz

Posted
Posted

24mb is not too bad for firefox sometimes it will go up to 90mb or so - at which point it is usually about to crash.

I do use tonnes of extensions though and 4 or so tabs open.

There are definite memory leak problems though - and it would be nice if they fixed them.

Grand Master

uniacidz

Posted
Posted
What a joke.  This is not a leak, this is thousands of leaks.

First version of the browser, so thousands of memory leaks are ok?  Please spare me the BS.  Memory leaks are NEVER okay.  There is an acceptable range, but 6,000 is NOT an acceptable range, nor is 14,000.

Making sure memory is properly managed should be a TOP PRIORITY for any software.

well, if you didnt close the program, and that stayed there, then it's not a leak

it's a leak if the memory isnt freed, so if you close that other tab, the memory usage doesnt go down.

But yeah, there is a slight problem with firefox's memory, you can change a option to make it use a max of 16MB a tab, it's in about:config, called cache something.

PLEASE READ WHAT I ALREADY SAID.

1. This was the report for after the application had been closed

2. This is memory that was not freed when it should have been

3. I only loaded 2 tabs, and refreshed each page twice. This should not cause such harsh memory problems.

585515096[/snapback]

Gotta agree with you there.

To me, just isnt good enough either. Saw this in the beta stages and then in final release. I dont see how they couldve released FF how it is.

I totally agree, poor

Mentor

vcv

Posted
  • Author
Posted
most of those apparent leaks are from mostly from the same place....anywho I submited your info so that people that better understand all that mumbojumbo and decipher it.

woah just seen you said this was after you closed the program!? something is wrong with your profile then becuase Firefox does not keep memory after it's closed

585515104[/snapback]

You don't understand how the profiler works then. It keeps track of memory allocated and deallocated. When the program closes, it sees which memory was freed and which was not.

24mb is not too bad for firefox sometimes it will go up to 90mb or so - at which point it is usually about to crash.

I do use tonnes of extensions though and 4 or so tabs open.

585515108[/snapback]

This has nothing to do with the memory usage during the application run.
Mentor

vcv

Posted
  • Author
Posted
what are the links to the pages you loaded? and also what extensions/themes are you using? and please try again when todays nightly is built

585515124[/snapback]

http://google.picasa.com/

http://www.news.com/

Extensions:

I have about 20 installed. I will run again on a clean install. However, extensions are not responsible for the memory management, FF is. So this is still a problem regardless of whether or not its the extensions.

I will also try a nightly build.

Jeesh this guy again I swear I think this guy is on microsofts payroll. go back read this guys posts and you'll see what i mean. Ok it has memory leaks so what. its still a good browser.
Please stay out of this thread if you're going to troll like this.

Guess what? I don't use IE, I hate it. So there goes your theory.

Grand Master

ZZOOzzoo

Posted
Posted
This is just the first version of this browser.  Give it some time before you complain about the memory leak.

585515088[/snapback]

Firefox has had many preview versions before this final 1.0 release.

It's had enough time to fix it, and apparently it's not.

:sleep:

585515119[/snapback]

:rolleyes:

What are you, a sleepy troll?

Grand Master

+Xinok Subscriber²

Posted
  • Subscriber²
Posted (edited)

I can confirm Firefox 1.0 has memory leaks, I've had problems with it before. I was looking through wallpapers on Deviantart before, and I don't think Firefox properly freed the wallpapers after I closed the tab, so it would easily use over 100mb after a few minutes.

Edit: Downloaded the latest nightly build of Firefox, tested on a fresh profile, the leak is still there :pinch: I'll be submitting the bug now.

Edited by xinok
Proficient

mircleman

Posted
Posted

guy im too old to play silly games and troll. I stated a view in my mind and why I said such is all everytime I turn around you are in a ff forum downgrading and trying to argue why it sucks and doesnt have this or that. Thats all. then I come on here this am and what do I see you again talking about ff. if thats trolling then so be it.

Mentor

vcv

Posted
  • Author
Posted
Wow, that's alot of leaks.... Have you tested other browsers too?

How long did you wait until running the test after you closed it? It may be freed later on...

585515150[/snapback]

I tested Opera and IE. Both had under 10 leaks (2 and 9).

I only ran firefox for 60-90 seconds and closed it. Once the process was gone from my list, I looked at the memory leaks. Firefox can not free memory once it is closed.

guy im too old to play silly games and troll. I  stated a view in my mind and why I said such is all everytime I turn  around you are in a ff forum downgrading and trying to argue why it sucks and doesnt have this or that. Thats all. then I come on here this am and what do I see  you again  talking about ff. if thats trolling then so be it.

585515154[/snapback]

Guess what? I use Firefox daily and have recommended it to many people. Try again.

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Posts

    • UK nudity blockers are a looming privacy disaster, we must be able to see the source code

      By zikalify · Posted

      UK nudity blockers are a looming privacy disaster, we must be able to see the source code by Paul Hill Image via Pexels The UK government, just like many state governments in the US and national governments around the world, has begun going on a bit of a power trip when it comes to digital safety. The major step taken so far is the introduction of the Online Safety Act, which requires users to prove their age to access adult websites (it includes more than this, too). Now, UK PM Keir Starmer is calling on Apple and Google, and presumably other mobile OS makers, to scan phones for explicit images to protect children. This potentially mandatory on-device scanning by vendor-controlled software will create unacceptable harms to individual freedoms and transparency, and introduce massive surveillance risks. In a statement on June 8, the Prime Minister stated that big tech companies, such as Apple and Google, must add features to their platforms, such as iOS and Android, that will detect and block sexually explicit or nude images involving under-18s on phones or tablets. Adults who want to take or send nudes would be required to hand over some form of identification to stop their phone from blocking these pictures, creating unnecessary privacy risks. According to the government, it wants to see these measures implemented within three months; otherwise, the government will introduce legislation to force them to introduce such technology. The legislation will include fines for companies and maybe even criminal liability for tech bosses who do not comply with the measures. In its announcement, the government said that stopping users from taking, sending, or receiving nudes without verifying their age is technically feasible, and pointed to a British firm called SafeToNet, which has made proprietary, closed-source, uninstallable software called HarmBlock and is actively selling a device with it enabled and is working with other OEMs. The fact that this software is closed source is a huge problem because it’s a black box; you do not know what it is doing on your device. The fact that it is unremovable is also a problem because you lose control of a phone that you own. Laughably, the government, just before highlighting SafeToNet, says that companies must introduce such measures “without threatening privacy or collecting any data.” It then says over-18s will still be able to view adult content by providing proof of age… Which sounds to me like data collection. SafeToNet makes some debatable claims about HarmBlock The government’s example software, HarmBlock, is a hugely alarming choice to espouse the virtues of this type of software. SafeToNet claims that HarmBlock is “ethically developed,” but this is the opposite of the truth. This black box software puts digital handcuffs on you if it’s installed in your device, taking away your freedom to control what software runs on your device, as it cannot be removed. It is not even free software, so we cannot inspect the source code to see what it is doing. For all we know, it could be acting maliciously. While that’s unlikely, we can’t verify that it’s not doing that. When Google and Apple do inevitably integrate these features on devices in the UK, they are very likely to be closed-source binaries, which will also be non-auditable. They will also have identity services built into them, which will require at least temporary collection of sensitive identity documents to verify your age. One saving grace for Android users is that this nudity blocker will very likely be implemented within the Google Play infrastructure that’s deeply tied into commercial Android devices. However, anyone with enough determination to throw out Google apps from their phone by flashing a custom ROM could find they regain control over their phone again without these digital handcuffs. Obviously, this is only how I expect Google to implement the feature; if it bakes it into the open-source Android somehow, that would be bad news for anyone looking to escape it. Outside of stripping mobile phone users of their freedom and sovereignty over their devices, these proprietary on-device machine learning or hash-matching solutions cannot be independently audited. This means that hackers could potentially exploit them because security researchers can’t investigate the code, and they could overstep their intended use case and collect even more user data without anybody knowing. We also wouldn’t know if the code is prone to detecting false positives or biased classification, because we can’t see the code. In the government’s announcement, contributing comments from the Internet Watch Foundation keep talking about “on-device protections” as if to say that users don’t need to worry about server-side processing; however, this is misleading, as data could flow from devices for the purpose of updates, remote model changes, telemetry, or server-side matching. We’ve also seen with the Online Safety Act that the government is never content with the laws it introduces; it always wants to expand the controls. If this scanning functionality arrives on devices, it might only block nudes initially, but later governments could pressure vendors for expanded access or use mandated features for other surveillance aims. The introduction of on-device scanners opens the door to massive risks in the future. Once nude blocking becomes normalized, regulators like Ofcom or politicians themselves could push for more controls over people’s devices. Very possible candidates for blocking include hate speech, misinformation, or undesirable political content. Also, there is a chance that once Apple and Google have developed this software, they might attempt to reuse the infrastructure for commercial or foreign requests, putting customers in greater danger. Just the UK's demand for this sets a precedent. What if a dictatorship decides to spy on activists by demanding that Google or Apple implement similar controls? Another concern with this scanning is that it adds compliance costs for businesses looking to get into the mobile operating system space. While Google and Apple dominate the space right now, there are lots of smaller companies creating mobile operating systems too, including community projects with very shallow pockets. How are these smaller competitors supposed to implement sophisticated nudity detectors? Simply put, they can’t. Then the government goes after them, causes them to shut down, and Google and Apple have less competition. Image via Aurora Store For us users who value sovereignty over our technology, this development will force us to seek freedom-respecting alternatives. The simplest path forward will likely be to install a custom ROM on an Android device; however, kicking Google off the phone with its black box nudity blocker could also make it harder to access apps such as banking apps, which tend to need you to pass Google's integrity checks. Thankfully, Google Play Store apps can still be obtained by storefronts such as the Aurora Store, but it just adds to the friction. To be fair to those pushing this measure to protect children, I think it will be reasonably effective, but people will still try to find ways around it, just as they’ve done with age gates on adult websites introduced under the Online Safety Act. In the effort to find circumvention methods, it could lead users to join riskier platforms that introduce new dangers. This effort also diverts resources from proven interventions such as law enforcement cooperation, targeted investigations, education, and support services to broad technical controls that have uncertain effectiveness (due to their newness). If the government is set on introducing such tools, then there ought to be safeguards in place. Any mandated code should be released as free software so that it can be audited, and the binaries should be reproducible builds so that the public knows nothing has been tampered with in the code used to create the binaries shipped out. Ideally, these tools should also be voluntary, opt-in, and even community-run. This would also allow people to have full control over their hardware while allowing parents to flip a switch to turn on these protections for children, with the knowledge that the code being run is doing exactly what it says on the tin, and nothing nefarious, like a black box solution could be doing. The government should also have a narrow legal scope where this technology stays with blocking nudes and not spreading to blocking political opinions, hate speech, and so on. Ideally, any implementation should avoid identity-linked age verification to keep user data safe, and matching should be done locally with no server telemetry to ensure it is truly on-device. While I do understand that stakeholders such as parents want to keep children safe, the potential for abuse with this type of software is colossal. It would entrench black-box surveillance and take away our freedom to use our devices as we want. There is also the acute risk that the government will demand this surveillance be expanded to block other activities, which could be particularly dangerous. If you are in the UK and don’t wish to see these measures implemented, it is still possible to write to your MP, which could lead to some better safeguards being introduced before it’s too late. Once we get more technical information about how this will be implemented, then we will be able to see if de-Googling Android devices will bypass this measure. For anyone with an iPhone, there is zero chance that you’ll be able to take off these handcuffs because Apple doesn’t let you mess with your software.
    • Apple would rather delay Siri AI than open iOS to rival assistants in the EU

      By Malisk · Posted

      I'm reading the reports as EU rejecting Apple's proposal because Trusted System Agent would be an intermediary offered to third party AI's (this article is also worded as such) but Siri AI itself would not pass this intermediary. This would cause a situation where Siri AI would have more direct system access and offer it an unfair advantage. (speaking from EU regulator perspective here) Apple is citing security issues with doing what EU asked for, and I think this also supports this theory, because truly direct system access like Siri AI would make it impossible to control third party AI's running on the devices and e.g. reign them in via adjustments to Trusted System Agent. So, I _think_ this is the sticking point right now: EU saying they need to be on equal footing as Siri AI, Apple saying they can't be because Apple only trusts their own AI. Apple could of course be leaning a bit extra hard towards this because they're biased in terms of excluding competitors. One method to find an agreement would be to have Siri AI also run through Trusted System Agent and treat it as untrusted. This kind of defensive architecture design (especially when involving an AI) would honestly not be a very bad idea from a sheer engineering standpoint. But then Apple would need to swallow their pride and adapt worldwide due to EU, and make perhaps major updates delaying Siri AI once more.
    • Politically funny images of the World

      By PsYcHoKiLLa · Posted

    • Halo: Campaign Evolved is out next month with new prequel missions

      By mcloum · Posted

      I have not even heard of that game. will take a look
    • Chasys Photo 5.41.01

      By Copernic · Posted

      Chasys Photo 5.41.01 by Razvan Serea Chasys Photo is a suite of image editing applications including a layer-based image editor with adjustment layers, linked layers, timeline and frame-based animation, icon editing, image stacking and comprehensive plug-in support (Chasys Photo Editor), a fast image viewer (Chasys Photo Viewer) and a fast multi-threaded image file converter (Chasys Photo Converter) , with RAW image support in all components. It supports the native file formats of several competitors including Adobe Photoshop, Affinity Photo, ArtWeaver, Corel PhotoPaint, FireAlpaca, GIMP, Krita, Paint.NET, PaintShop Pro and Pixlr, and the whole suite is designed to make effective use of multi-core processors, touch-screens and pen-input devices. Designed under the mantra of “unique, flexible and powerful”, Chasys Photo takes a radically different approach to image editing with the aim of opening up new possibilities for those who dare to be different. Chasys Photo key features: Free-style layering with blending modes Adjustment layers with multiple adjustments per layer Linked layers (a.k.a Linked Smart Objects) Composite, Image List, Frame Animation and Object Animation image modes Animation, both frame-based and object-based (timeline animation) Animation Composer engine Image Stacking for noise reduction, super-resolution, etc. Tablet/Pen-input/Stylus support with pressure control Touch-screen support with gestures including pitch-to-zoom and multi-finger panning Support for the native formats of Adobe Photoshop, Affinity Photo, ArtWeaver, Corel PhotoPaint, FireAlpaca, GIMP, Krita, Paint.NET, PaintShop Pro and Pixlr Support for common formats such as JPEG, animated PNG, animated GIF, TIFF, PICT, WebP, HEIF, DDS, JPEG-2000, JPEG-XR, JPEG-XL, AVI video, etc. Support for the OpenRaster interchange file format and rare formats such as QOI, MNG/JNG and DPX Support for older formats such as PPM/PGM/PBM, PCX/DCX, PCD, TGA, COKE, etc. Comprehensive Camera RAW file support with live adjustment Extensive plug-in support with streamlined SDKs Support for Photoshop Filter Plug-ins (.8BF) Advanced printing and scanning engines PDF document generation Icon and cursor editing, import and export, including Vista-style and Mac-OS icons Screen Capture, including Video Screen Capture with multiple triggering modes Video capture from devices (e.g. TV/Video) Supports multi-core processors, High-DPI displays and Multiple Display setups Integrated File Browser, Bluetooth OBEX and in-built utilities (Calculator, Notepad) Shell integration with thumbnails and conflict detection Unlimited Undo/Redo and Asynchronous Auto-Save, with Just-in-time memory compression to save space Fully re-editable text with advanced styling and effects (TextArt) Full alpha channel through out the workflow with Alpha protection (a.k.a. transparency protection) Multiple language support with user-editable language files and translation assistant (Chasys Photo Language Studio) Anti-aliasing and super-sampling support in tools and paths* Smart-resizing (similar to seam-carving) Best-in-class post-edit heuristics anti-aliasing engine Physical measurement specification with display size detection via EDID Uses the latest CD5 specification with animation and multi-resolution Super-fast internal graphics engine (JpDRAW2) Full UNICODE support in all components Metadata save, restore and scale to imitate vector art Configurable Guides and Grids with Snap-to-Grid Smart-dither to custom palette Asynchronous preview rendering engine Pantone equivalent palettes for PMS 100 to 814-2x Automatic color naming ... and many more! Chasys Photo 5.41.01 changelog: New Features Layered images with multiple pages (Composite/Multi-page) Additional templates to support template-centric workflow New Layer Blend Mode: Inverse Luma Mask Horizon detection in Rotate Transform Cropping option when importing video Orientation options in QR Code Generator plug-in Solved angle ambiguities (CCW versus CW) Internal Improvements Improved graphics engine (JpDRAW2™ v26.05) Improved CD5 codec (v4.10, improved ACSC compression) Improved interpolation when downsizing images Improved motion detection in Video Capture Slightly lower memory usage (RAM is getting expensive!) File Support and Bug Fixes Improved PXZ file support (placeholders, blanks) [bug-fix] Memory leak in flt_JPEG.dll Download: Chasys Photo 5.41.01 | 46.1 MB (Freeware) View: Chasys Photo Home Page | Wikipedia Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware

  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient

  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      83
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!