From: "Doug Bissett" <ecs-isp@2rosenthals.com>
Message-ID: <100.885a09003a34e768.006@ocii.com>
To: "eCS ISP Mailing List" <ecs-isp@2rosenthals.com>
Date: Wed, 08 Oct 2025 22:04:10 -0600 (MDT)
Reply-To: "Doug Bissett" <dougb007@ocii.com>
In-Reply-To: <list-14391121@2rosenthals.com>
References: <list-14390617@2rosenthals.com>
  <list-14391121@2rosenthals.com>
Priority: Normal
User-Agent: PMMail/3.26 (os/2; U; Warp 4.5; en-CA; i386; ver 3.26.00.2018)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [eCS-ISP] Weasel 3.08

On 2025-10-08, at 17:42:15, Steven Levine wrote:
>
>In <list-14390617@2rosenthals.com>, on 10/08/25
>   at 12:07 PM, "Doug Bissett" <ecs-isp@2rosenthals.com> said:
>
>Hi Doug,

Hi...

>>>Offhand, it looks like weasel ran out of heap memory and weasel did not
>>>catch the allocation failure and the resulting null pointer. One
>>>interesting feature of the modula-2 runtime is that the heap size is fixed
>>>when the binaries are built.  This means that weasel can run out of heap
>>>space while there are still large amounts of OS/2 address space available.
>
>>Since I am the only user, I would find that theory to be unlikely.
>
>I understand that you are the only user.  However, threads use address
>space, even if they are doing nothing.  A thread that is processing a
>message is going to use more, but that's expected.
>
>With the addition of DKIM and TLS support the per thread memory usage has
>increased a bit.  A thread count that was OK in older Weasel versions
>might be too much under some conditions in 3.08.

I have not, yet, played with DKIM or TLS. I use weasel for two things. One is to test PMMail, the other is to relay outgoing mail to my ISP's server. The failure was doing my nightly send to test PMMail. Nothing fancy, just send mail.

>IAC, I took another look at the errinfo.$$$ and this changed the results
>of my analysis.
>
>Your trap occurred while processing an SMTP AUTH command and it looks like
>a defect in the semaphore handling logic.  I'll explain what I think I am
>seeing to Peter, when he returns.

That makes a little more sense. FWIW I have had older weasel versions terminate a few times. The indication was that it was doing AUTH. I never found any real information to pass on, and since it terminated, it was automatically restarted.

>>I
>>should mention that the client, and server, are connected by a gigabit
>>LAN, which may have something to do with it.
>
>Unlikely.  This does not look like a data rate issue.
>
>>The bad part is, that it did not terminate, so it was not restarted
>>automatically.
>
>This is another feature of the Modula-2 runtime.  This kind of exception
>restarts the failing thread, but this typically is not sufficient get keep
>weasel working properly.
>
>Steven

Thanks again...

-- 
**************************** 
From Doug Bissett's ArcaOS system 
dougb007 AT ocii.com 
**************************** 
... Don't sweat the petty things. Don't pet the sweaty things.