On Wed, Nov 8, 2017 at 10:52 AM, African Wild Dog
wrote:
> 2017-11-07 23:57 GMT-02:00 Michael Van Canneyt :
>>
>> ...
>>
> My environment: Linux Debian Stretch 64 bits - Lazarus 1.6.4 - fpc 3.0.2.
>
> I'm quite impressed with the processing power of fastcgi fcl-web
> applications: they consume lit
On Wed, 8 Nov 2017, African Wild Dog wrote:
2017-11-07 23:57 GMT-02:00 Michael Van Canneyt :
The "memory leak" is the exception object: you are not catching the
exception.
Change your program to the below, and you'll see that it is not leaking
memory in the XML routines itself.
Michael.
2017-11-07 23:57 GMT-02:00 Michael Van Canneyt :
>
> The "memory leak" is the exception object: you are not catching the
> exception.
>
> Change your program to the below, and you'll see that it is not leaking
> memory in the XML routines itself.
>
> Michael.
>
In fact, protecting with Try..Excep
On Tue, 7 Nov 2017, African Wild Dog wrote:
Hello,
Using ReadXMLFile function from XMLRead unit generates memory leaks when
trying to read a invalid XML content.
The "memory leak" is the exception object: you are not catching the exception.
Change your program to the below, and you'll see
XMLDocument.Free;
end;
end.
Note: when I tried your original code in Lazaur method, it didn't leak at all.
V.
__
> Od: African Wild Dog
> Komu: FPC-Pascal users discussions
> Datum: 07.11.2017 23:19
> P
Hello,
Using ReadXMLFile function from XMLRead unit generates memory leaks when
trying to read a invalid XML content.
CODE
program xml_leak_test;
uses
heaptrc,
Classes,
DOM,
XMLRead;
var
XMLDocument: TXMLDocument;
InvalidStream: TStringStream;
const
INVALID_XML_CONTENT
