From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 14391120 for ecs-isp@2rosenthals.com; Wed, 08 Oct 2025 21:22:00 -0400 Received: from secmgr-va.2rosenthals.com ([50.73.8.217]:57790 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1v6fLq-000000007uj-1QOL for ecs-isp@2rosenthals.com; Wed, 08 Oct 2025 21:21:50 -0400 Received: from mta-201a.earthlink-vadesecure.net ([51.81.229.180]:35433) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1v6fLf-0000000060y-0hSu for ecs-isp@2rosenthals.com; Wed, 08 Oct 2025 21:21:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=WzLBoxZuuvDV3soGsme1ZAT5/eOG4sfh9fn2Zp hHmO8=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-unsubscribe-post: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=dk12062016; t=1759972898; x=1760577698; b=fJ4lgl9Udu2ftlxJZmREWTj2H6x SxCh5W9X76IQcH2o0LNCRYSX81/a7p9eu+iJRz+qYgx+wEagohB3jPyFftscLYT747+16GP tRtgPsMnsK2LvLnFbeaufEehOA3yuhHV0KB8MOw88EB3Yz08/zvlJGUKEQfvLxb6YI8YDqw i1pd2wpITiHKmOku4sdsoirdiviz0tT8nvurwLP/n8SgAW+xk/Vgxw/DEAxtNbkwioLpAdd CwbDmq+hxf1EJfsnukUuBJm+zilWbq7M2fC/VCW5A7elV+jgkY6WFFmZPJqj05FoW9jnxmi ShqW/FP3HoCtYEYPXDCOTB7HJM5IRbA== Received: from slamain ([107.202.224.188]) by vsel2nmtao01p.internal.vadesecure.com with ngmta id a3bb42ba-186cae069d68de28; Thu, 09 Oct 2025 01:21:38 +0000 Message-ID: <68e712f7.22.mr2ice.fgrirsq@earthlink.net> Date: Wed, 08 Oct 2025 17:42:15 -0800 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] Weasel 3.08 X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 10/08/25 at 12:07 PM, "Doug Bissett" said: Hi Doug, >>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. 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. >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 -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------