[Cuis-dev] Space is low
Gerald Klix
cuis.01 at klix.ch
Sat Aug 10 08:14:23 PDT 2024
Hi Juan,
I just tried version 6578:
Once save the (Cuis) image with a display extent of 4320 at 3840
and restart it, I get a huge memory consumption
some X11 errors and some VM errors.
As with Haver I have to set a resource limit on the available
memory otherwise my machine will become unresponsive.
Is there anything – logs, sys-traces, what ever – I can provide to help?
Best Regards,
Gerald
--- snip ---
bear at speedy ~/H/Cuis7XBased> squeak --version
5.0-202312181441-HVR_MVP_ALPHA5_WINKEY_2024-01-24 Wed Jan 24 10:28:30
CET 2024 clang-13 [Production Spur 64-bit x86_64 VM]
CoInterpreter VMMaker.oscog-eem.3339 uuid:
b1c834e2-5de7-464c-aeb5-4f2a7b8812d6 Jan 24 2024
StackToRegisterMappingCogit VMMaker.oscog-eem.3339 uuid:
b1c834e2-5de7-464c-aeb5-4f2a7b8812d6 Jan 24 2024
VM: 202312181441-HVR_MVP_ALPHA5_WINKEY_2024-01-24
bear at speedy:gitwork/opensmalltalk-vm
Date: Mon Dec 18 15:41:18 2023 CommitHash: 72a81c50c
Plugins: 202312181441-HVR_MVP_ALPHA5_WINKEY_2024-01-24
bear at speedy:gitwork/opensmalltalk-vm
Linux speedy 5.10.0-27-amd64 #1 SMP Debian 5.10.205-2 (2023-12-31)
x86_64 GNU/
--- snip ---
bear at speedy ~/H/Cuis7XBased> squeak Cuis7.1-6578-w1.image -v
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 132
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 161
System information:
Cuis7.1
latest update: #6578
Running at :/home/bear/HaverWorks/Cuis7XBased/Cuis7.1-6578-w1.image
--- snap ---
bear at speedy ~/H/Cuis7XBased> ulimit -a
Maximum size of core files created (kB, -c) 0
Maximum size of a process’s data segment (kB, -d)
unlimited
Control of maximum nice priority (-e) 0
Maximum size of files created by the shell (kB, -f)
unlimited
Maximum number of pending signals (-i) 127799
Maximum size that may be locked into memory (kB, -l) 64
Maximum resident set size (kB, -m)
unlimited
Maximum number of open file descriptors (-n) 1024
Maximum bytes in POSIX message queues (kB, -q) 800
Maximum realtime scheduling priority (-r) 2
Maximum stack size (kB, -s)
8192
Maximum amount of CPU time in seconds (seconds, -t)
unlimited
Maximum number of processes available to current user (-u) 127799
Maximum amount of virtual memory available to each process (kB, -v)
20000000
Maximum contiguous realtime CPU time (-y) unlimited
bear at speedy ~/H/Cuis7XBased> ulimit -v
20000000
--- Schnipsel ---
bear at speedy ~/H/Cuis7XBased> squeak Cuis7.1-6578-w1.image
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 132
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 162
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 183
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 212
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 238
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 289
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 340
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 369
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 420
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 449
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 500
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 529
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 580
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 609
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 660
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 689
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 740
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 769
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 820
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 849
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 901
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 926
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 977
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 1006
sqAllocateMemorySegmentOfSizeAboveAllocatedSizeInto mmap: Cannot
allocate memory
sqAllocateMemorySegmentOfSizeAboveAllocatedSizeInto mmap: Cannot
allocate memory
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 1059
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 1088
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 1139
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 1168
shmat: Cannot allocate memory
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 1343
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 1495
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 1669
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 1948
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 2122
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 2403
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 2582
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 2861
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 3050
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 3331
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 3530
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 3813
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 4248
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 4400
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 4836
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 4928
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 4959
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 4999
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 5437
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 5589
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 6025
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 6050
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 6101
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 6126
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 6177
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 6202
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 6253
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 6278
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 6330
X Error: BadWindow (invalid Window parameter)
Major opcode of failed request: 3
Minor opcode of failed request: 0
Serial number of failed request: 6482
^C⏎
On 8/10/24 12:07 PM, Gerald Klix via Cuis-dev wrote:
> I have similar issues with my Haver images,
> when I use my two UHD monitors together
> (Display extent: 4320 at 3840).
>
> Funny enough it never happens with a pristine Cuis image,
> there for I was convinced that I introduced that bug
> and did not report it.
>
>
> Best Regards,
>
> Gerald
>
>
>
> On 8/7/24 10:08 PM, Juan Vuletich via Cuis-dev wrote:
>> Hi Folks,
>>
>> Yesterday Jon Raiford saved an image that did something similar to
>> what you Mark describe when starting it, moving it to a 5k display,
>> and setting it full screen. We spent several hours debugging
>> together. The result is updates #6569 and #6570, pushed today to
>> GitHub. These updates do fix the issue as experienced by Jon. I'm
>> pretty confident they'd fix what you Mark saw too.
>>
>> Thank you Jon for finding a case we could reproduce, and for
>> debugging it together!
>>
>> Cheers,
>>
>> On 7/25/2024 10:38 AM, Mark Volkmann via Cuis-dev wrote:
>>> It finally happened again. I have attached two screenshots, one
>>> showing the exception and one showing Transcript output that Juan
>>> requested.
>>>
>>> On Thu, Jul 18, 2024 at 9:08 AM Mark Volkmann
>>> <r.mark.volkmann at gmail.com <mailto:r.mark.volkmann at gmail.com>> wrote:
>>>
>>> The "Space is low" issue hasn't repeated itself for me in the past
>>> couple of days, but I'll report back if it does happen again. I
>>> did pull down the latest updates to Cuis a couple of days ago, so
>>> I suppose it's possible there was a recent change that fixed this.
>>>
>>> On Thu, Jul 18, 2024 at 2:48 AM Barry Perryman
>>> <barry.perryman at gmail.com <mailto:barry.perryman at gmail.com>> wrote:
>>>
>>> What happens when you minimise cuis before letting it go to
>>> sleep?
>>>
>>> I'm asking because this is what happens on my Mac - M2 Mini
>>> running Sonoma with LG 4K screen.
>>>
>>> I usually run Cuis as a window - so not full screen. When the
>>> system goes to sleep, or the display sleeps, it quite often,
>>> although not always, will resize the window to a smaller size.
>>> Cuis isn't the only application that this happens to; citrix
>>> client will also have the same issue, again not every time,
>>> even though that is run as full screen. I've always figured
>>> this is some mac sleep quirk that I have to live with.
>>>
>>> I haven't had the issue occur when I minimise the cuis window
>>> - although I have had the icon on the dock look like it's been
>>> resized - so instead of a 128x128 icon it's shrunk to say a
>>> 80x60 icon (guess).
>>>
>>> Next time few times it happens I'll grab the size because now
>>> I think about it I'm fairly sure the resize looks to be about
>>> the same size every time.
>>>
>>> I've not reported this before because I've never been able to
>>> consistently reproduce it.
>>>
>>> Barry
>>>
>>>
>>>> On 18 Jul 2024, at 01:16, Mark Volkmann via Cuis-dev
>>>> <cuis-dev at lists.cuis.st <mailto:cuis-dev at lists.cuis.st>>
>>>> wrote:
>>>>
>>>> A sleep of the Mac was involved.
>>>> I didn't move the window myself after it woke up, but I do
>>>> have it on a second monitor, so when it wakes up I suppose
>>>> macOS "moves it".
>>>> My Mac has slept several times today and did not result in a
>>>> low memory exception on waking.
>>>> I inserted the logging code that Juan requested.
>>>> Perhap it will happen again tomorrow morning. I'll report
>>>> back if it does.
>>>>
>>>> On Wed, Jul 17, 2024 at 2:02 PM Nicolás Papagna Maldonado via
>>>> Cuis-dev <cuis-dev at lists.cuis.st
>>>> <mailto:cuis-dev at lists.cuis.st>> wrote:
>>>>
>>>> Just thinking out loud here.
>>>>
>>>> Based on what Juan mentioned, did you move the Cuis
>>>> window between monitors (assuming that triggers a resize)?
>>>>
>>>>
>>>> On Wed, Jul 17, 2024 at 3:45 PM Andres Valloud via
>>>> Cuis-dev <cuis-dev at lists.cuis.st
>>>> <mailto:cuis-dev at lists.cuis.st>> wrote:
>>>>
>>>> Did the machine (partially) go to sleep in those 2
>>>> hours? Does the
>>>> problem manifest when the machine transitions between
>>>> sleep and awake?
>>>>
>>>> On 7/17/24 11:36, Juan Vuletich via Cuis-dev wrote:
>>>> > This is not normal at all.
>>>> >
>>>> > The allocation that shows in the walkback you
>>>> posted happens at the
>>>> > start of #mainLoop. This method is only called when
>>>> the Morphic system
>>>> > needs to be reinitialized, usually because the main
>>>> Cuis window was
>>>> > resized and a new Canvas needs to be created. It
>>>> should not happen if
>>>> > you just let the machine idle for a couple of
>>>> hours. And it is not
>>>> > possible to know what's going on without further
>>>> information. So, please:
>>>> >
>>>> > - Keep the Transcript open and visible
>>>> > - Add this line at the start of
>>>> #spawnNewMorphicProcessFor:, after the
>>>> > temp declaration.
>>>> > thisContext printStack: 10.
>>>> >
>>>> > #spawnNewMorphicProcessFor: should only be called
>>>> when the main Cuis
>>>> > window is resized. So keep the Transcript visible
>>>> and see if a stack
>>>> > trace gets printed even if you're not resizing the
>>>> Display. If this
>>>> > happens, please post the result.
>>>> >
>>>> > Thanks,
>>>> >
>>>> > On 7/16/2024 10:44 PM, Mark Volkmann via Cuis-dev
>>>> wrote:
>>>> >> See my replies inline below. Could this be related
>>>> to the fact that I
>>>> >> have the tiger SVG displayed on the desktop with
>>>> this?
>>>> >>
>>>> >> SVGMainMorph exampleTiger openInWorld.
>>>> >>
>>>> >> On Tue, Jul 16, 2024 at 8:29 PM Andres Valloud via
>>>> Cuis-dev
>>>> >> <cuis-dev at lists.cuis.st
>>>> <mailto:cuis-dev at lists.cuis.st>
>>>> <mailto:cuis-dev at lists.cuis.st
>>>> <mailto:cuis-dev at lists.cuis.st>>> wrote:
>>>> >>
>>>> >> And, what are the arguments to
>>>> setExtent:depth:?
>>>> >>
>>>> >>
>>>> >> extent: 3456.0 at 1440.0
>>>> >> bitsPerPixel: 32
>>>> >>
>>>> >> On 7/16/24 18:27, Andres Valloud via Cuis-dev
>>>> wrote:
>>>> >> > Interesting. What's the argument to basicNew:?
>>>> >>
>>>> >>
>>>> >> sizeRequested is 4976640
>>>> >>
>>>> >> > On 7/16/24 18:25, Mark Volkmann via Cuis-dev
>>>> wrote:
>>>> >> >> Here's a screenshot of the stack trace.
>>>> >> >>
>>>> >> >> On Tue, Jul 16, 2024 at 8:19 PM Andres Valloud
>>>> via Cuis-dev
>>>> >> >> <cuis-dev at lists.cuis.st
>>>> <mailto:cuis-dev at lists.cuis.st>
>>>> <mailto:cuis-dev at lists.cuis.st
>>>> <mailto:cuis-dev at lists.cuis.st>>
>>>> >> <mailto:cuis-dev at lists.cuis.st
>>>> <mailto:cuis-dev at lists.cuis.st>
>>>> <mailto:cuis-dev at lists.cuis.st
>>>> <mailto:cuis-dev at lists.cuis.st>>>>
>>>> >> wrote:
>>>> >> >>
>>>> >> >> No, that's not normal. Can you paste the
>>>> debugger's stack
>>>> >> here?
>>>> >> >>
>>>> >> >> On 7/16/24 18:11, Mark Volkmann via
>>>> Cuis-dev wrote:
>>>> >> >> > Usually when I leave Cuis Smalltalk running
>>>> and walk
>>>> >> away from my
>>>> >> >> > computer (macOS) for a couple of hours, when
>>>> I come back
>>>> >> there
>>>> >> >> is a
>>>> >> >> > Debugger window open with the message "Space
>>>> is low". I
>>>> >> can just
>>>> >> >> close
>>>> >> >> > it and keep working. Everything seems fine.
>>>> Is this normal?
>>>> >> >> >
>>>> >> >> > --
>>>> >> >> > R. Mark Volkmann
>>>> >> >> > Object Computing, Inc.
>>>> >> >> >
>>>> >> >> -- Cuis-dev mailing list
>>>> >> >> Cuis-dev at lists.cuis.st
>>>> <mailto:Cuis-dev at lists.cuis.st>
>>>> <mailto:Cuis-dev at lists.cuis.st
>>>> <mailto:Cuis-dev at lists.cuis.st>>
>>>> >> <mailto:Cuis-dev at lists.cuis.st
>>>> <mailto:Cuis-dev at lists.cuis.st>
>>>> <mailto:Cuis-dev at lists.cuis.st
>>>> <mailto:Cuis-dev at lists.cuis.st>>>
>>>> >> >> https://lists.cuis.st/mailman/listinfo/cuis-dev
>>>> >> <https://lists.cuis.st/mailman/listinfo/cuis-dev>
>>>> >> >> <https://lists.cuis.st/mailman/listinfo/cuis-dev
>>>> >> <https://lists.cuis.st/mailman/listinfo/cuis-dev>>
>>>> >> >>
>>>> >> >>
>>>> >> >>
>>>> >> >> --
>>>> >> >> R. Mark Volkmann
>>>> >> >> Object Computing, Inc.
>>>> >> >>
>>>> >> --
>>>> >> Cuis-dev mailing list
>>>> >> Cuis-dev at lists.cuis.st
>>>> <mailto:Cuis-dev at lists.cuis.st>
>>>> <mailto:Cuis-dev at lists.cuis.st
>>>> <mailto:Cuis-dev at lists.cuis.st>>
>>>> >> https://lists.cuis.st/mailman/listinfo/cuis-dev
>>>> >> <https://lists.cuis.st/mailman/listinfo/cuis-dev>
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> R. Mark Volkmann
>>>> >> Object Computing, Inc.
>>>> >
>>>> >
>>>> > --
>>>> > Juan Vuletich
>>>> > cuis.st <http://cuis.st/>
>>>> > github.com/jvuletich <http://github.com/jvuletich>
>>>> > researchgate.net/profile/Juan-Vuletich
>>>> <http://researchgate.net/profile/Juan-Vuletich>
>>>> > independent.academia.edu/JuanVuletich
>>>> <http://independent.academia.edu/JuanVuletich>
>>>> > patents.justia.com/inventor/juan-manuel-vuletich
>>>> <http://patents.justia.com/inventor/juan-manuel-vuletich>
>>>> > linkedin.com/in/juan-vuletich-75611b3
>>>> <http://linkedin.com/in/juan-vuletich-75611b3>
>>>> > twitter.com/JuanVuletich
>>>> <http://twitter.com/JuanVuletich>
>>>> >
>>>> >
>>>> -- Cuis-dev mailing list
>>>> Cuis-dev at lists.cuis.st <mailto:Cuis-dev at lists.cuis.st>
>>>> https://lists.cuis.st/mailman/listinfo/cuis-dev
>>>>
>>>>
>>>>
>>>> --
>>>> Nicolás Papagna
>>>> -- Cuis-dev mailing list
>>>> Cuis-dev at lists.cuis.st <mailto:Cuis-dev at lists.cuis.st>
>>>> https://lists.cuis.st/mailman/listinfo/cuis-dev
>>>>
>>>>
>>>>
>>>> -- R. Mark Volkmann
>>>> Object Computing, Inc.
>>>> -- Cuis-dev mailing list
>>>> Cuis-dev at lists.cuis.st <mailto:Cuis-dev at lists.cuis.st>
>>>> https://lists.cuis.st/mailman/listinfo/cuis-dev
>>>
>>>
>>>
>>> -- R. Mark Volkmann
>>> Object Computing, Inc.
>>>
>>>
>>>
>>> --
>>> R. Mark Volkmann
>>> Object Computing, Inc.
>>
>>
>>
>
More information about the Cuis-dev
mailing list