Which version of the build are you using? I think I fixed this on head a while back ... but this hasn't been released yet. If you are compiling your own copy, well then I'll have to dig back into it.
The threads are being spawned todo the parsing, and were not being killed when the feature_reader was left alone. I do not believe you have runaway threads (infinite looping of yields / waits), just some unwanted memory. Basically this cannot be completely fixed, because you don't always know when someone is finished with the reader.
The fix in question had todo with the handling getting the FeatureSchema, which originally would have left threads hanging around at times.
Please let me know,
David
On 2/9/06, Sean McGowan <[EMAIL PROTECTED]> wrote:
Hi there,
Does anybody know how I can stop the memory leak in GMLDataStore? From
reading a previous answer, a possible solution is to close the fcbuffer
thread in GMLDataStore. Does anybody know where in the code I can do this?
I'm not very experienced with Java threads ;-)
Thanks,
Sean
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
