On 2025-10-07, at 23:18:47, Steven Levine wrote:
>
>In <list-14383008@2rosenthals.com>, on 10/07/25
> at 09:54 PM, "Doug Bissett" <ecs-isp@2rosenthals.com> said:
>
>Hi,
Hi to you...
>>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.
Since I am the only user, I would find that theory to be unlikely. I should mention that the client, and server, are connected by a gigabit LAN, which may have something to do with it.
>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.
I never changed the defaults. I will try to find time to read the paper. If it happens again, I will consider switching to the 100 Mb LAN connection, to slow it down.
The bad part is, that it did not terminate, so it was not restarted automatically.
>
>Steven
Thanks...
--
****************************
From Doug Bissett's ArcaOS system
dougb007 AT ocii.com
****************************
... I was always taught to respect my elders. Now I don't have anyone to respect.
back to list