Enter one-line summary

[GoogleCodeExporter]

On any Mac running OS 8.6, 9.0x, 9.1.x, 9.2.x in native mode Memory is not 
freed once it has been allocated (tested on a wide range of Macintosh 
hardware).  Of cource this causes a heavy hit on performance (and low end Macs 
are already underpowered for mozilla) and eventualy the memory allocated 
overruns the window assigned to Classizilla (or on macs with less DRAM to run 
completely out of Mem) causing various strange crashes.  This is reproducibale 
on all realeases of Classilla to date.

NOTE: This condition does not seem to cause as much trouble on newer PowerPC 
systems running 'Classic Envirement' under OS X.

Original issue reported on code.google.com by kd0tpc1...@gmail.com on 7 Feb 2011 at 3:45

[GoogleCodeExporter]

I'm closing this Invalid for two reasons:

- Bugs from users should be sent through Report-A-Bug for triage to keep this 
worklist focused.

- Not that your observations are incorrect, but this is a combination of memory 
leaks in multiple areas, so this is not "one bug". Specific ones are being 
stamped out, and the new layout engine in 9.3.0 (issue 1) should help. 
Unfortunately I am painfully aware of the memory issue.

I do appreciate the report, however.

Original comment by classi...@floodgap.com on 7 Feb 2011 at 3:53

• Changed state: Invalid

[GoogleCodeExporter]

Thank you.� I only posted this as I was unable to find any open bugs in the 
trac that accounted for this.�� I know that I am different than most 
developers, though I would not release a compiled binary of any project if 
there were any known memory leeks.� There is nothing that I pay closer 
attention to than bounds checking (NOT RELYING ON THE COMPILER, All bounds 
checking should be done manually [as this is usually faster than that of a 
compiler, and always more reliable]), and tracking memory allocation (to be 
sure that any allocated block is freed as soon as no longer needed).� Also if 
you are using any C++ or other Class/Object oriented language memory allocation 
and should be done manually when creating/deleting instances of a class.��� But 
this is just the way I code.

PS: For me it is simpler to work with classes and OO in C or Assembly than to 
use an "Object Oriented Language", as most OO lang compilers do a very poor job 
at resource tracking for the allocation and freeing of classes.

Original comment by kd0tpc1...@gmail.com on 11 Feb 2011 at 5:56

[GoogleCodeExporter]

Classilla/Mozilla is an enormous project, about 31,000 source files and 337 MB 
uncompressed, 99% of which is inheirited code, so checking all of it before 
release would probably have delayed the release for years.  I would much rather 
have the browser with some leaks than not at all.

When browsing some sites, it's a non-issue; I can use the browser for hours 
over many days and memory usage doesn't increase significantly.  Eventually the 
mac crashes for some other reason.

With other sites, Classilla will inflate itself like a balloon and eventually 
explode after about half an hour, but iCab 3.05 and Opera 5/6 typically can't 
get into those sites at all.

Original comment by sakuya...@lavabit.com on 16 Feb 2011 at 5:49

[GoogleCodeExporter]

Subsequently, I noticed this behavior while using Firefox (Iceweasel) under 
Debian, so I checked bugzilla.mozilla.org.  There are currently about 261 bugs 
that come up for the search, "memory leak".  Likewise, a web search for firefox 
+ "memory leak" produces plenty of results covering various versions of Firefox.

...So, it's not just a Classilla problem, there are plenty of them in the 
upstream codebase, and even the Mozilla project with its legions of developers 
is having trouble controlling them.

It could be handy if Classilla would automatically detect that it was running 
out of memory and put up a dialog offering to save the open windows & quit.  
For one thing, the cache wouldn't be lost; Mozilla invalidates the cache on the 
next startup if it exited by crashing, which is a separate issue that has been 
open for about 9.5 years.
(https://bugzilla.mozilla.org/show_bug.cgi?id=105843)

Original comment by sakuya...@lavabit.com on 7 Mar 2011 at 9:06