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 14383037 for ecs-isp@2rosenthals.com; Wed, 08 Oct 2025 02:43:39 -0400 Received: from [192.168.200.201] (port=55395 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.98.2) (envelope-from ) id 1v6Nti-000000007Xy-22LA for ecs-isp@2rosenthals.com; Wed, 08 Oct 2025 02:43:39 -0400 Received: from mta-101a.earthlink-vadesecure.net ([51.81.61.60]:56055) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1v6Nth-000000001Ty-05QZ for ecs-isp@2rosenthals.com; Wed, 08 Oct 2025 02:43:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=NI8+SJ2gnYPgWddAG9cAIOWnVcwCR9O9S2fM+u VMgys=; 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=1759905816; x=1760510616; b=rkPQlB8nMyvImzVVIEGoN68zM1E NftNfPB8/dMEpk49n+FHUREB5bCW/OKB+k5I9viLydgOxA8C+pAkI+d+ERMlW8m7zTFyCzk 7kvZ92MWVkJRRWH4Aw+s8ghq3/mzD7FjMKbIU845GFpTGuqGmV7C9KqJlaqScWpGovtYqVe 4qCyVRumKYlnks/dS5uOzcwgu/sQNUx+Z3XK3z+Vw/VlCsW7aNi/m5IOigS2XYriK4GfhlF coY+LAuK5hrnoyN/AcXykap9gzxp48kIz6FFsk3hjgWx+Nv2A8Wjlj0iZ1bp70AT8uOr7DU 0nccWbAUHv0uBb9IvUV6yl/iYVigigA== Received: from slamain ([107.202.224.188]) by vsel1nmtao01p.internal.vadesecure.com with ngmta id 2208ae3a-186c7103e2eb3e66; Wed, 08 Oct 2025 06:43:36 +0000 Message-ID: <68e61057.14.mr2ice.fgrirsq@earthlink.net> Date: Tue, 07 Oct 2025 23:18:47 -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/07/25 at 09:54 PM, "Doug Bissett" said: Hi, >I got an error while running Weasel 3.08. >2025_10_07_21_34!05_M_499_tib_ord is what was in the window. errinfo.$$$ >is attached. I find no other information. >Any thoughts? 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 heaop space while there are still large amounts of OS/2 address space available. However, looking at the code I cannot see how the pointer was null when other related code used he pointer sucessfully. We shall see what Peter has to say when he returns. While it may not be related, I notice you have a lot of threads running. Several years ago Peter wrote a paper (92.MailTuning.pdf) explaining how to calculate the optimal number of threads. The paper can be found in the papers page on Peter's website. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------