Re: [Wrapper-user] Memory leak calling getLastErrorText()

[Leif M. <lei...@ta...>]

Tim,
I wanted to follow up as well.  The getLastErrorText method is known to
have a small leak, but it is not normally called repeatedly.
Where it is we are specifically freeing the returned string.

What is the version you are seeing the leak in?  Is it something that you
have been able to reproduce?
There have been some other leaks fixed over time:
http://wrapper.tanukisoftware.com/doc/english/release-notes.html

Cheers,
Leif


On Tue, Sep 9, 2014 at 4:34 PM, Alexandre Klein <
ale...@ta...> wrote:

> Tim,
>
> Thank you for your email.
> We are aware of this issue with getLastErrorText() and it is in our bug
> tracking system.
>
> We will fix it in a future version of the Java Service Wrapper.
>
> If you see any other problem in our code, please let us know. We really
> want to improve the Wrapper and deliver a great product to our users.
>
> Regards,
> Alexandre Klein
>
> On Fri, Sep 5, 2014 at 9:37 PM, Tim Lammens <tim...@gm...> wrote:
>
>> Hi,
>>
>> We are using your wrapper and sometimes the wrapper itself goes out of
>> memory.
>> It seems when the method getLastErrorText() in the C code of the wrapper
>> is called, the memory allocated with malloc is not being freed afterwards.
>> Is this possible or did I miss something?
>>
>> Regards,
>> Tim
>>
>