I thought memory leaks were just bugs in the code where memory that was allocated for something isn't allocated when its done...something like:
for(i=0;i<1000000;i++) {
void *mem = malloc(1024);
// I don't feel like deallocating this memory so I'll just eat 1Gb of RAM real quick
}
Depends on who allocated it and for what -- whether it was allocated on the heap or the stack and whether the thread that was responsible for it still lives or not. Now that I think about it, that was one of the problems I seem to recall Mozilla having. Not cleaning up after their threads. And if a thread dies with memory allocated, it's completely orphaned. Not necessarily attached to the main process ID. The other thing is, as I pointed out and others have as well, if it's a resource leak, it would be in X and not in Mozilla. My suspicion is that it's probably a combination of both. Or even more than that, it could be other applications (helpers) as well, depending on how you run Mozilla. Bottom line is that Mozilla has for years been a big, steaming pile of crap and rather than streamlining it, the developers keep adding and adding to the codebase. Oh, I should add IMO.
Ric
-- [EMAIL PROTECTED] mailing list
