Garbage collector memory leak "feature"?

[nick.b]

Bill Baxter wrote:
> nick.b wrote:
>>
>> There have been a lot of excellent posts on this issue, and 
>> suggestions on how this issue could be fixed/corrected.  I have one 
>> question:  Has anyone posted this as a bug ?
> 
> I posted a bug about AA's causing memory exhaustion (with a test case). 
>  If you're talking about a bug where false pointers on the stack cause 
> memory exhaustion, I don't think anyone has actually run across such a 
> case in practice.
> 
> --bb
Bill - the original post on this issue was by David Brown on 9/10/2007 
at 5:04am.  I have copied part of his original post below:

"I've been developing an application on x86_64 (dgcc) without any problems.
Yesterday, I tried building it on x86 to discover that it has a memory 
leak on that platform.  The leak is rather significant, and the program 
quickly exhausts memory and is killed.

Any suggestions from the list on how to debug/fix this? "

I tracked all the posts on this issue.
The following day David posts some more details. Here is a snip of his 
post:

"Hmm, the keys of my hash were all stored in an AA.  At least the AA 
only  has the first 4 bytes of the hash rather than the whole thing."


So, thanks for posting the bug with the test case. I had thought there 
was an outstanding issue, but this does not seem to be the case.

Nick