[fdo-users] Memory leaks - lots of them ?

[Oyvind Idland]

I tracked just one leak, and it appears to come from the FDO framework
itself.

I'm not in my office right now, but I also saw a SAFE_ADDREF macro or
something
like that being used on the same pointer during the callstack, could it be
ref's that doesn't
get released ? (didn't study in detail)


-- Oyvind



On Tue, Feb 22, 2011 at 4:39 PM, Greg Boone <greg.boone at autodesk.com> wrote:

>  The FDO API is fairly good when it comes to controlling memory. The
> ArcSDE provider itself may not be as efficient. If you have any details,
> please send them and/or create a trac ticket.
>
>
>
> Greg
>
>
>
> *From:* fdo-users-bounces at lists.osgeo.org [mailto:
> fdo-users-bounces at lists.osgeo.org] *On Behalf Of *Oyvind Idland
> *Sent:* Tuesday, February 22, 2011 10:18 AM
> *To:* FDO Users Mail List
> *Subject:* [fdo-users] Memory leaks - lots of them ?
>
>
>
> I get lots of memory leaks when debugging the trunk code.
>
> Is there being done any checks for leaks by the coders ?
>
> Let me know if you need some more info.
>
>
>
> -- Oyvind
>
> _______________________________________________
> fdo-users mailing list
> fdo-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-users/attachments/20110222/cd5423c2/attachment.html