Firefox 1.0 has major memory leaks

[arrrgh]

Thanks for the laugh

[Jimny]

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

No it's not. Obviously you have no knowledge of this topic at all.

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

585515096[/snapback]

And knowing what you're talking about should be a TOP PRIORITY for anyone starting a new thread. In essence what you're doing is trolling. Everybody knows that firefox has memory leaks, you know that the firefox fanboys will deny it, so you start a thread about it. It's not wanted.

[vcv]

No it's not.  Obviously you have no knowledge of this topic at all.

Really? How so? Please point out any of what I have said to be false.

And knowing what you're talking about should be a TOP PRIORITY for anyone starting a new thread.  In essence what you're doing is trolling.  Everybody knows that firefox has memory leaks, you know that the firefox fanboys will deny it, so you start a thread about it.  It's not wanted.

585516454[/snapback]

Ok.. this is a bit different actually. This involved a multitude of leaks in a matter of 60-90 second usage. The problem everyone knows of is with using it for extended periods of time and having it keep using more and more memory.

This thread was not an attempt to troll at all. I'm sorry if you think so, but you're not me.

[vcv]

I imagine your browser uses the IE shell. Why code your own? I'm not trying to be a dick, I'm just curious is all.

Uhhhhhhhhhhhhh no I dont use an I.E. shell or any other shell I  designed it and me and few others coded it I dont use any thing ms cept on one machine. everything is mine/my companys. and before you ask no we dont code it in C or any variation of  c or any  known computer language for that matter. thats why we dont have the issues we do that most others do.

585516421[/snapback]

Well mind even stating what the language is called? What platform? What does it support? I'm honestly curious. I've given thought to doing basic browser prototypes and if you really have designed your own browser, I wouldn't mind asking a few questions.

[xxdesmus]

When I used Firefox, mine was hitting around 200+ MB of ram with two or three tabs open using no extensions.

The product is a complete failure at this version number.

585515812[/snapback]

3 tabs open, several extensions, 24MB of ram....hmm....

[Fred Derf Veteran]

3 tabs open, several extensions, 24MB of ram....hmm....

585516517[/snapback]

Open a site that has hundreds of high res images in those three tabs. That's not really the memory usage that he's talking about.

I believe the thread starter is talking about memory being wasted after FF is closed (or so I think). I've never noticed that problem nor do I think it is a big deal.

[mircleman]

Well mind even stating what the language is called? What platform? What does it support? I'm honestly curious. I've given thought to doing basic browser prototypes and if you really have designed your own browser, I wouldn't mind asking a few questions.

First off even though the language doesnt officially haave a name yet we are calling it X for right now. it will run on both IBM and apple machines so cross platform. When we set out to do it we decided on few basic things. 1. had to be different then all other browsers, with more features and fuctionality. 2. it had to demonstrate our

belief that you can have 100% secure and safe. anyway it took us about 2 1/2 years and we have been testing it quietly here internaly and in real world enviroments. if you wanna ask questions pm me or e mail id be happy to answer whatever. c( cept for screenshots and code samples in few months perhaps ) :)

[E t h a n]

Personally I like firefox and don't notice any memory leaks that may be there. I'm not a fanboy or anything, but I just see no performance hit or anything. I suppose I use firefox because it seems safer than IE, but I also like it. Hopefully if this memory problem is big, it'll bet fixed! :rofl:

[Jimny]

Really?  How so?  Please point out any of what I have said to be false.

I already did, but I'll repeat it since you didn't read my other post: your claim that firefox has thousands of memory leaks is a lie.

you're not me.

Thanks for the clarification. How old are you, eight?

Did you even read that log you posted? I don't see anywhere that evidences thousands of memory leaks.

[pacifica]

did you have any extensions installed? i noticed that when i have certain extensions installed i get poorer performance than if i had no extensions installed.

[vcv]

I already did, but I'll repeat it since you didn't read my other post: your claim that firefox has thousands of memory leaks is a lie.

No, it's not.

Did you even read that log you posted?  I don't see anywhere that evidences thousands of memory leaks.

585516569[/snapback]

Maybe you should think before you post. Each one of those IS a memory leak.

did you have any extensions installed?  i noticed that when i have certain extensions installed i get poorer performance than if i had no extensions installed.

585516570[/snapback]

Yes, I had a bunch of extensions installed. I'm trying to zero in on which one may have caused it, but I'm having trouble with freezes at the moment.

[scaredmogwai]

i'm getting the high memory usage too.

Firefox 1.0, 4 Extensions and 2 tabs open.

i like firefox a lot but i always wonder what causes this.

[vcv]

Be aware that the high mem usage there may not be the same thing. Firefox may in fact free that memory, it's hard to say.

[Jimny]

your claim that firefox has thousands of memory leaks is a lie.

No, it's not.

585516588[/snapback]

Well then why don't you provide some evidence to support your claim?

Each one of those [lines in log] IS a memory leak

Actually thats a lie also. That log is a list of all the times firefox allocated memory, not of memory leaks. You really have no idea what you are talking about. Really no idea.

[RufioPan]

I've found that Tabbrowser Preferences slows down a Moz installation quite a bit, although I've not tried it on Firefox, so I can't be sure.

As for the memory leaks that vcv found, I don't know why he's getting so much heat for it. If anyone is unhappy with this thread, or thinks he's trolling, then just leave the thread. You don't have to sit here and complain about it.

To add something more constructive to the issue: it does seem likely that the memory leaks are relating to extension management by the Moz framework. A lot of the extension management functionality seemed to have been added to Firefox in the last 2 or 3 point releases of the app, although I'm not a Moz developer so I wouldn't know if this would cause memory leaks or lead to higher probability of leakage.

As well, could the answer to extension manager problems (including memory leaks) be in a revamp of the way extensions are registered and handled? The Mozilla Wiki section on chrome registration mentions some problems associated the current chrome registration system and that the revamp should address those issues. Again, I can imagine that this might be related to memory leaking in relation to the extension management system, but of course, this is speculation on my part.

Would be great to hear from someone involved with the Mozilla project, if anyone here occupies such a role. :)

[ECEGatorTuro]

I've been reading through this thread and some people just don't understand what is going on.

vcv is stating that memory is not being freed up when FF closes. He is not talking about runtime memory allocation!

How many times are people going to ask that question?! :blink: :s

[vcv]

Well then why don't you provide some evidence to support your claim?

Uh.. I did. The export log, the screen shot. Anyone can run the program on Firefox for themselves as well.

Actually thats a lie also. That log is a list of all the times firefox allocated memory, not of memory leaks. You really have no idea what you are talking about. Really no idea.

This is really infuriating. Have you used the program?

IF what you say is true (which it is NOT), then why do other programs only show a few things in that list after they are closed? Do you not see the caption of the window that says "Leaks Result".

----------

Now.. I tried this with the latest nightly and TBE installed (nothing else).

I have the homepage set to default (google).

I Opened a new tab, and clicked the home button in the new tab.

When the page was finished loading, I closed the first tab.

I repeated this 10 times. I wanted to see if loading the same page causing it to keep using more memory.

Results:

2829 leak(s) found in 3.624 seconds.

So I think it's narrowed down a bit. I'll play around more and see if I can get some more progress on it.

[vcv]

FF Nightly / TBE Extension

Refreshed home page once, closed FF.

6 leaks found

FF Nightly / TBE Extension

Created new tab with double click, closed FF.

7 leaks found

FF Nightly / TBE Extension

Created new tab with double click, clicked home page button, closed FF.

8 leaks found

FF Nightly / TBE Extension

Created new tab, clicked home page, closed original tab, closed FF.

2881 leaks found

FF Nightly / TBE Extension

Created new tab, home page, closed 2nd tab then first, closed FF.

7 leaks found

-----

Very peculiar results. I repeat each test twice to make sure, and got the same results. I repeated the 2nd last one 5 times with the same results.

Can anyone else try these to see if they get similar results?

edit: Tried same thing with TBE uninstalled, same results. So it doesn't appear to be TBE.. and no other extensions are installed.

[Rablet]

Can anyone else try these to see if they get similar results?

585516747[/snapback]

Yeah, give me a link to the program you were using to test it and I'll be glad to try :)

[vcv]

Yeah, give me a link to the program you were using to test it and I'll be glad to try :)

585516783[/snapback]

http://www.glowcode.com/eval.htm

It's full features for 15 days I think.

[WinCC]

vcv:

Why don?t you download the source code , take a quick look through it , fix the leaks,compile it, run your test again and provide us with a link to a fresh nonleaking Firefox build , I?ll be back tomorrow ,downloading your fixed version...:woot:t:

Regards WinCC

[Rablet]

This is what I got.

I'm not sure this is what you were looking foor though :wacko: :huh:

[bkellner]

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.

585515129[/snapback]

First off, it seems you have no idea how things work. Let me explain to you then..

Firefox loads pages into memory. When Firefox closes, most of it's memory allocations are deallocated. Extensions CAN allocate their own memory, and if badly coded, may not close them. Firefox cannot be held accountable for all it's third party extensions.

Plus nowadays we a thing called Virtual Memory. This makes memory leaks much MUCH less of a problem. Memory leaks aren't *real* memory leaks until all your virtual memory is depleted. How often is this a problem? Rarely. With Firefox? Never.

[Help]

Yes there is a memory leak in FF, usually happens when you use tabs.

Regarding the memory eating by FF..... found the following at http://forums.mozillazine.org/viewtopic.php?t=172041

"type about:config into the location bar, press enter, right click any line, choose "new">"integer", paste this into the dialogue that appears:

browser.cache.memory.capacity

click okay, specify the amount in kb in the next dialogue that appears, restart firefox. -LeRoi"

[bkellner]

You originally stated that this is not an attempt to troll, rather an attempt to warn others about Firefox's major memory leaks.

According to your own tests and results:

Firefox does not have "thousands" of memory leaks like you originally stated. In fact, Firefox has less than 10 memory leaks. It is Firefox's third party extensions that have thousands of memory leaks.

Yet you still claim you are right and that Firefox has major memory leak problems. After your own tests revealed Firefox does not have major memory leak problems, you still contest that it does. This sounds more like trolling than a warning to me.