On Mon, 5 Oct 2009, Lee Jenkins wrote:
Does anyone else have any trouble reading heaptrc output? The only thing
that I can see of use is that it tells me there /is/ a leak. However, trying
to figure out where it is according to heaptrc output seems more difficult
and time consuming that
Michael Van Canneyt wrote:
On Mon, 5 Oct 2009, Lee Jenkins wrote:
Does anyone else have any trouble reading heaptrc output? The only
thing that I can see of use is that it tells me there /is/ a leak.
However, trying to figure out where it is according to heaptrc output
seems more
2009/10/5 Lee Jenkins l...@datatrakpos.com:
Does anyone else have any trouble reading heaptrc output? The only thing
that I can see of use is that it tells me there /is/ a leak. However,
trying to figure out where it is according to heaptrc output seems more
difficult and time consuming
Lee Jenkins wrote:
Definitely related to TXMLDocument. Apparently, it is either a complete
mess and fraught with memory leaks or am misunderstanding how to use
it. Although, its not the first XML API I've used.
Once again, its back to Delphi I go :-(
Your trouble looks like issue
On Mon, Oct 5, 2009 at 16:41, Lee Jenkins l...@datatrakpos.com wrote:
Does anyone else have any trouble reading heaptrc output? The only thing
that I can see of use is that it tells me there /is/ a leak. However,
trying to figure out where it is according to heaptrc output seems more
Sergei Gorelkin wrote:
Lee Jenkins wrote:
Definitely related to TXMLDocument. Apparently, it is either a
complete mess and fraught with memory leaks or am misunderstanding how
to use it. Although, its not the first XML API I've used.
Once again, its back to Delphi I go :-(
Your
Just one thing in case you don't know already. There is a package
leakview (it's included in lazarus, but not installed by default (afaik))
Once installed , it appears in the tools menu, and you can load the
leak-trace output. it will display similar like the stack view, allowing
you to click
Michael Van Canneyt wrote:
On Mon, 5 Oct 2009, Lee Jenkins wrote:
Sergei Gorelkin wrote:
Lee Jenkins wrote:
Definitely related to TXMLDocument. Apparently, it is either a
complete mess and fraught with memory leaks or am misunderstanding
how to use it. Although, its not the first XML
Lee Jenkins escreveu:
Michael Van Canneyt wrote:
On Mon, 5 Oct 2009, Lee Jenkins wrote:
Does anyone else have any trouble reading heaptrc output? The only
thing that I can see of use is that it tells me there /is/ a leak.
However, trying to figure out where it is according to heaptrc
Sergei Gorelkin wrote:
Lee Jenkins wrote:
I'll give it a try. I'm updating my snapshot installation of Lazarus
on Windows, though I'm not sure if the fix will be included.
Also, Node.NextSibling doesn't seem to work either as it seems to
return the exact same node and results in an endless
Lee Jenkins wrote:
Now, for my own personal education:
(skipped)
In the above trace, it looks like (and I have confirmed) the leak occurs
inside of the LoadMappings method when I was using the TXMLDocument
object before updating my lazarus snapshot, but I am curious as to why
the
Sergei Gorelkin wrote:
Lee Jenkins wrote:
Now, for my own personal education:
(skipped)
In the above trace, it looks like (and I have confirmed) the leak
occurs inside of the LoadMappings method when I was using the
TXMLDocument object before updating my lazarus snapshot, but I am
12 matches
Mail list logo
