[Cuis-dev] Space is low
Juan Vuletich
juan at cuis.st
Fri Jul 26 13:47:13 PDT 2024
It crashed when asking for a mere 20MB, on a machine that has likely no
less than 8GB of RAM. And it happened in #checkForNewScreenSize. Somehow
the OS window for Cuis is of different size than it was, maybe because
sleeping / awaking is moving it between physical displays.
It looks like this is happening many, many times in a short time. I
suggest tweaking the hacks to also record the timestamps this
#newUIProcess happens, and to count the number of times. Sending
Transcript to stdout will be handy when contents is too large for the
visible Transcript, or in case the image stops responding. You can test
those hacks by resizing the OS Cuis window. Also, start Cuis from a
command line, so you can see stdout.
If #newUIProcess is not happening many times, then (or in any case), it
is relevant to monitor the memory consumption of the Cuis process with
OS tools.
We need to learn if there are a large number of spurious allocations
(and then we need a fix to avoid that), or if a single 20MB allocation
is enough to run out of memory. If the latter, is the machine / OS
memory starved? Is Cuis taking gigabytes of ram for some other reason?
Keep us posted on your debugging activities!
Thanks,
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.
--
Juan Vuletich
cuis.st
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich
linkedin.com/in/juan-vuletich-75611b3
twitter.com/JuanVuletich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20240726/50305281/attachment-0001.htm>
More information about the Cuis-dev
mailing list