[mapguide-internals] detecting dangling feature readers

Walt Welton-Lair walt.welton-lair at autodesk.com
Sat May 23 02:45:30 EDT 2009

Just to clarify, it's technically not a leak - the reader's destructor does call Close.  The problem occurs ifyou use .NET code in your web tier.  The managed readers in the web tier don't get garbage collected right away, and this can lead to a buildup of cached readers on the serve (this was the "leak" reported in the ticket).  Once GC kicks in the web-tier proxy readers are destroyed / closed, and this also cleans up the corresponding readers on the server.

Nevertheless, it's still good practice to call Close as soon as you're done with the reader.  I don't know of any API which can enumerate the open readers.

From: mapguide-internals-bounces at lists.osgeo.org [mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Zac Spitzer [zac.spitzer at gmail.com]
Sent: Friday, May 22, 2009 11:58 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] detecting dangling feature readers

just following up on this ticket

it's there any method available to enumerate open readers
to detect these kind of leaks?

Zac Spitzer -
+61 405 847 168
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org

More information about the mapguide-internals mailing list