[nos-bbs] Jnos memory leak with forwarding

[Boudewijn (Bob) Tenty]

Yes, it is with incoming forwarding but what also plays a role here I think is when the indexing is messed up and this happens sometimes with a large area
like 'ww' (@ww),  .idn and .new files are formed and jnos doesn't know what to do with it as it seems or the area is too large to fix the indexing.
Is it running out of resources?

Bob VE3TOK


On 2017-10-18 12:12 PM, Brian wrote:
> I've seen it on rare occasions. It's as if the incoming forward goes into a loop state and creates files of massive size before it gives up. I haven't seen it in a while though and a reload seems to help fix it. Of course you also need to go through your mail files because the grunge forward will append to your stored bulletin files. It was more prone in 2.0k.0
> ---
> Pardon my brevity, I'm on a Samsung Galaxy Note 3.
> Sent via the axMail-FAX suite.
>
>
>
> On October 17, 2017 8:26:48 PM "Michael Fox - N6MEF" <n6mef at mefox.org> wrote:
>
>> Bob,
>>
>> I've been running 2.0k.1 for months, and haven't seen that.  Is there a particular condition that you think triggers it?  In other words, is it when JNOS initiates forwarding?  receives forwarding?  To/from certain types of forwarding partners?  Does it return to normal after forwarding?
>>
>> BTW, some of our machines are using 2.0k.1 (with our usual set of DEFINEs) and some have an updated lzhuf.c which includes some diagnostics to help find a problem with LZ decoding that causes the mailbox to blow up to 10s of Mbytes of garbage.  Unfortunately, after installing the new code, whatever was causing it hasn't occurred again.
>>
>> Michael
>> N6MEF
>>
>>> -----Original Message-----
>>> From: nos-bbs [mailto:nos-bbs-bounces at tapr.org] On Behalf Of Boudewijn
>>> (Bob) Tenty
>>> Sent: Tuesday, October 17, 2017 3:16 PM
>>> To: TAPR xNOS Mailing List <nos-bbs at tapr.org>
>>> Subject: [nos-bbs] Jnos memory leak with forwarding
>>>
>>> Forwarding with the latest jnos version is using an enormous amount of CPU
>>> cycles. (80 -90 %)
>>> This slows down that computer so much that it is extremely difficult to
>>> login with ssh
>>> when that happens. I think that it looks like a memory leak.
>>>
>>> 73,
>>>
>>> Bob VE3TOK
>>>
>>> _______________________________________________
>>> nos-bbs mailing list
>>> nos-bbs at tapr.org
>>> http://www.tapr.org/mailman/listinfo/nos-bbs
>>
>> _______________________________________________
>> nos-bbs mailing list
>> nos-bbs at tapr.org
>> http://www.tapr.org/mailman/listinfo/nos-bbs
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs