[Cuis-dev] Space is low
Gerald Klix
cuis.01 at klix.ch
Mon Aug 12 05:40:52 PDT 2024
Hi Juan,
I tested the this issue with FreeBSD on the same
(development) machine and with Devuan Daedalus
on another machine.
My development machine runs Devuan Chimaera.
It works perfectly on the other machine.
With FreeBSD 14 the same error occurs.
The VM for FreeBSD is essentialy the Linux VM,
I only disabled the frame-buffer interface.
FreeBSD has the newest X-Server version.
I presume this is related to a buggy X11 implementation
or some X11 protocoll corner case the VM does not handle
correctly. Since I can not provide instructions to reproduce
this issue – after all it works with Xephyr – I suggest
I'll watch this issue and when I'll find some means to reproduce it
I'll file an error.
HTH,
Gerald
PS: Just before sending this e-mail,
I tried the same stunt with the Squeak 6 version at
hand. It works.
--- X11 versions ---
Hape02
======
Referred to as „the other machine“.
bear at hape02 ~> sudo Xorg -version
X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
Current Operating System: Linux hape02 6.1.0-23-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.99-1 (2024-07-15) x86_64
Kernel command line: BOOT_IMAGE=/@rootfs/boot/vmlinuz-6.1.0-23-amd64 root=UUID=9abcba3f-4d1e-43d7-b63d-a132346c8301 ro rootflags=subvol=@rootfs quiet
xorg-server 2:21.1.7-3+deb12u7devuan1 (https://www.devuan.org/os/community)
Current version of pixman: 0.42.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Speedy
======
My „development machine“.
Linux
-----
bear at speedy ~ [127]> sudo Xorg -version
[sudo] password for bear:
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System: linux Debian
Current Operating System: Linux speedy 5.10.0-31-amd64 #1 SMP Debian 5.10.221-1 (2024-07-14) x86_64
Kernel command line: dozfs=force root=ZFS=zos/root/devuan pcie_aspm=off rw initrd=devuan\initrd.img-5.10.0-31-amd64
Build Date: 10 April 2024 08:59:35AM
xorg-server 2:1.20.11-1+deb11u13 (https://www.debian.org/support)
Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
FreeBSD
-------
bear at speedy ~ [1]> sudo Xorg -version
X.Org X Server 1.21.1.13
X Protocol Version 11, Revision 0
Current Operating System: FreeBSD speedy 14.1-RELEASE-p3 FreeBSD 14.1-RELEASE-p3 GENERIC amd64
Current version of pixman: 0.42.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
On Sat, 10 Aug 2024 23:10:07 +0200
Gerald Klix via Cuis-dev <cuis-dev at lists.cuis.st> wrote:
> Hi Juan,
>
> Yes it is consistent, hence the limited virtual memory.
>
> ad 1) This is not full-screen, it's exactly twice as much as your test
> machine,
> two 3840 at 2160 monitors in portrait mode side by side.
> If I safe Cuis/Haver in full-screen mode, this would be 2160 at 3840,
> which works fine. I also can use squeak -vm-display-X11 -fullscreenDirect
> corresponding to a display extent of 6240 at 3840. Sure enough the fault
> happens as described with this huge display.
>
> I tested it with the latest official squeak-vm, sure enough same problem,
> which is no surprise; my vm is derived from that one.
>
> Now comes the funny/sad part:
> In order to be helpful, I tried a setup with a virtual X-server (Xephyr).
> I wanted to provide some means to reproduce that bug on machines
> without a big screen.
>
> I can run it like this:
> Start Xephyr like Xephyr -screen 10000x10000 :1&,
> start a window manager in it (openbox), fire up the image
> save it in full-screen mode and it starts nicely in non-fullscreen-mode
> giving me a Display extent of 9992 at 9962.
>
> When I start this image with the saved big display using my normal X-Server
> the old heisenbug shows up again.
>
> It's now 22:40, tomorrow I will try this with FreeBSD on the same machine
> and on Linux using one of my two reserve development machines.
> Alas It also has an AMD-GPU, but an older one.
>
> ad 2) It did never happen with Cuis 7.0. It happens with Cuis 7.1
> version 6541.
> It always happens with Haver.
>
> ad 3) Did not test yet, but I suspect: No, I have this this issue with
> Haver for over an year now.
>
> ad 4) N/A
>
> ad 5) When I activate transcript to file in the image with 9992 at 9962
> running under Xephyr
> save it and restart it on my normal X server, the memory allocation loop
> finally terminates
> and I get the following transcript output:
>
> ----QUIT----(10 August 2024 22:47:31) Cuis7.1-6578-Xephyr.image
> priorSource: 1040586
> Not enough memory to run VectorEngine. Using BitBltCanvas instead.
> Display allocation failed
>
> AFAIR it normally fails in Form>>#setExtent:depth:
> line:
> newBits := Bitmap new: (self bitsSizeForWidth: newWidth height:
> newHeight depth: newDepth abs).
> but my memory might be wrong. I am aware that DisplayScreen>>#getMainCanvas
> is responsible for that transcript message.
>
>
> HTH,
>
> Gerald
>
>
>
> On 8/10/24 8:34 PM, Juan Vuletich wrote:
> > Hi Gerald,
> >
> > I assume you can reproduce this consistently. If so, there is hope.
> >
> > Some reasonable questions are: 1) does this happen only if you save in
> > full screen, but not if you save while in a regular OS window taking
> > all the display? 2) Did this happen with previous update level of
> > Cuis? 3) If so, is it related to updates #6569 and #6570? 4) What
> > happens if you take them back? 5) Did you have Transcript open? If
> > not, try again with Transcript open, and see if you get something there.
> >
> > I can't reproduce the problem, as it seems specific to your setup. I
> > use a MacBook with an externa 3840 at 2160 display. I can't reproduce the
> > problem, so now you can start debugging. See the code in #6569 and
> > #6570. Print stuff to Transcript, including `DateAndTime now print` to
> > see what's going on. You can also turn on "Transcript to file".
> >
> > It may turn up that this is a VM issue. I don't know. In any case, VM
> > maintainers will need a better report than "huge memory consumption,
> > some X11 errors and some VM errors".
> >
> > Hope this helps.
> >
> > On 8/10/2024 12:14 PM, Gerald Klix via Cuis-dev wrote:
> >> 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
> >>>
> >
>
> --
> Cuis-dev mailing list
> Cuis-dev at lists.cuis.st
> https://lists.cuis.st/mailman/listinfo/cuis-dev
More information about the Cuis-dev
mailing list