In reply to a post by AEP:

It is most certainly not undiscovered. Several people experience memory leaks with Firefox that are not blamed on addins.

Try to understand that all software and hardware has its faults. We have eonough of people blindly ignoring this fact as it is.

Find a blocking memory leak on bugzilla. Several people mistake normal memory build up for leaks, because they have no clue what they are talking about.

I suspect we have different ideas about what constitutes "sensible use of resources" and what the requirements are for "good code". There's a lot of idealism amongst those who are not dealing with software development in a commercial context or have no experience of working on sophisticated products. I've no idea if that is you or not. But complaining because Firefox is using 300 MB when you want it to use 150 MB is in that ballpark.

I certainly wouldn't wish to comment on the difficulties or otherwise of writing good code if I didn't have experience of doing so in a commercial environment. I've written such code for PCs and for mainframes using a variety of programming environments, and I like to think it was reasonably efficient.

In my experience it's a lot easier to write good code from the outset than to write indifferent code and then try to improve it.

In reply to a post by AEP:

In my experience it's a lot easier to write good code from the outset than to write indifferent code and then try to improve it.

Clearly. But that is hardly the point.

Mainframes with hole punch readers no doubt.

No. Punch cards and paper tape were before my time.

I suspect that you have no experience beyond PCs and are unfamiliar with other hardware. And I'm sure that you have no experience of programming in a commercial setting.

Commercial no, open source yes. Firefox is open source.

You'll have to excuse me if I decline advice from someone who can't tell the difference between assembler code and C code.

As I suspected, no idea of what is involved in writing software in a commercial environment.

Er, you were the one who claimed to have written the entire OS in Assembly. I was the one who pointed out that most of it was C.

In reply to a post by 12eason:

In reply to a post by Chrysalis:

On ff4, the ram usage just keeps going up whilst its idle, it keeps going up until you do something like close the active tab or load a new page in that tab, at which point the ram will go back down again (not necessarily all of it but most of it).

I don't get that. It would be a blocking bug too, but it's not on bugzilla. I'd imagine it's caused by a plugin or addon. The fact that it is in the javascript heap would point to that too.

there is at least 10 reports on bugzilla regarding memory leaks in ff4, my guess is there is actually at least triple that but 10 is what I found with a quick search. 2 of them are mine.

also on ff4 if its left idle for too long it eventually crashes with the memory usage, mine last crashed when idle for 14 days and 7.6gig of ram usage.