Re: [Help-smalltalk] Strategy to finding memleaks

[Paolo Bonzini]

On Sat, Apr 9, 2011 at 19:04, Holger Hans Peter Freyther
<address@hidden> wrote:
> On 04/09/2011 03:33 PM, Paolo Bonzini wrote:
>
>> After some time the first GC would happen and the result sets should
>> be gathered into an array and finalized. Then the second GC would
>> happen and the result sets would be collected.
>>
>> You can check: 1) if the finalizers are run; 2) who the owners are
>> after #finalize; 3) who the owners are for the array of objects to be
>> finalized, after its processing has ended.
>>
>> You have a talent for writing testcases, anyway!
>
> I failed so far with a standalone testcase.. in the real one we have max 5000
> Instances of DBI.PostgreSQL.PGResultSet. I think it is too much but that is
> not a bug.. so hypothesis one and two are... memory fragmentation or leak on
> the Postgres calls..

Leaks in C code should be "obvious" by comparing ObjectMemory values
with those from top(1).

Also they wouldn't be fixed by Smalltalk GC. :)

Memory fragmentation can be fixed by "ObjectMemory compact" without a
previous  GC.

Paolo