On Wed, Sep 21, 2016 at 7:44 PM, K leo <cnbiz...@gmail.com> wrote:
> I am running the 0.5 release now and it behaves in the same way - not
> releasing memory.  I can't say if this only has to do with 0.5 but not 0.4.
> Probably it happened in the same way with 0.4 but I just didn't pay
> attention then.
>
> Since there is no mechanism in Julia like in C/C++ for the programmer to
> free previously allocated memory, I don't believe that this is due to my
> coding errors (I only allocate memory without freeing them in the code).  I
> hope someone can point out to situations where this problem might occur so
> that I can check them out.  For now all I know is that my code allocates
> memory when it runs and those memory are not getting released even after the
> code has finished.
>
> I will try to see if I can cook up some demo code.

There's infinitely many ways mem leak bugs can happen. The only way
you can help debugging is to post actual code that reproduce the
issue. I personally don't care how long the code is, as long as it's
easy to run.

>
>
> On Wednesday, September 21, 2016 at 9:53:07 PM UTC+8, Páll Haraldsson wrote:
>>
>> On Sunday, September 18, 2016 at 12:53:19 PM UTC, K leo wrote:
>>>
>>> Any thoughts on what might be the culprit?
>>>
>>>   | | |_| | | | (_| |  |  Version 0.5.0-rc4+0 (2016-09-09 01:43 UTC)
>>>  _/ |\__'_|_|_|\__'_|  |  Official http://julialang.org/ release
>>
>>
>> You say 0.5 in the title (when 0.5 wasn't out). Your later posts are after
>> 0.5 is out. Maybe it doesn't matter, I don't know, maybe the final version
>> is identical (except for versioninfo function..), I just do not know that
>> for a fact, so might as well upgrade just in case.
>>
>> --
>> Palli.
>>
>>
>>
>

Reply via email to