|
| From: | Holger Hans Peter Freyther |
| Subject: | Re: [Help-smalltalk] Strategy to finding memleaks |
| Date: | Sat, 09 Apr 2011 19:04:18 +0200 |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Lightning/1.0b2 Thunderbird/3.1.9 |
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.. did you ever attempt to build the C code with boehmGC to detect leaks?
| [Prev in Thread] | Current Thread | [Next in Thread] |