kwin_wayland: ../libepoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed.
Hello list: I'm not a wayland power user. I need it though, to run a handful of instances that require it. The most relevant section (I think), is below. It happens as soon as an x number of programs (or sessions of the same program) are minimized to the panel. It doesn't matter whether the panel was created, selected as the default option, or it's customized. As soon as I hover over each minimized hidden window on the panel (or minimized hidden session of the same program), wayland, or kdeinit5 I guess, freezes, crashes and tries to restart, to no avail. thanks QImage::scaled: Image is a null image kf.baloo.engine: Running on 32 bit arch, limiting DB mmap to 1 GByte plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x2905a50) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x2905a50) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x2905a50) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x2905a50) plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. kwin_wayland: ../libepoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed. The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? (EE) failed to read Wayland events: Broken pipe kdeinit5: KLauncher died unexpectedly.
Re: kwin_wayland: ../libepoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed.
On Monday, 23 May 2022 11:07:35 PDT Carlos wrote:
> QImage::scaled: Image is a null image
This first line probably indicates an out-of-memory condition: some operation
prior to this failed to allocate memory for its image, so scaled() simply
complained that there was no image to scale. All the other errors after this
could be related, like:
> plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count.
This could be that it can't get the some information because the image was
null. But, looking at the code, it looks more like more memory allocation
failure:
EGLint count = 0;
EGLBoolean success = eglQueryDmaBufFormatsEXT(display, 0, nullptr,
&count);
if (!success || count == 0) {
qCWarning(PIPEWIRE_LOGGING) << "Failed to query DMA-BUF format
count.";
return {};
}
> kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x2905a50)
Ditto.
So my conclusion is that you're out of memory, most likely due to a memory
leak somewhere. All the error messages except for the kwin_wayland one from
plasma, so it could be a memory leak in plasma.
> kf.baloo.engine: Running on 32 bit arch, limiting DB mmap to 1 GByte
Why are you running on 32-bit?
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel DPG Cloud Engineering
Re: kwin_wayland: ../libepoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed.
On 5/23/22 16:01, Thiago Macieira wrote:
On Monday, 23 May 2022 11:07:35 PDT Carlos wrote:
QImage::scaled: Image is a null image
This first line probably indicates an out-of-memory condition: some operation
prior to this failed to allocate memory for its image, so scaled() simply
complained that there was no image to scale. All the other errors after this
could be related, like:
plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count.
This could be that it can't get the some information because the image was
null. But, looking at the code, it looks more like more memory allocation
failure:
EGLint count = 0;
EGLBoolean success = eglQueryDmaBufFormatsEXT(display, 0, nullptr,
&count);
if (!success || count == 0) {
qCWarning(PIPEWIRE_LOGGING) << "Failed to query DMA-BUF format
count.";
return {};
}
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x2905a50)
Ditto.
So my conclusion is that you're out of memory, most likely due to a memory
leak somewhere. All the error messages except for the kwin_wayland one from
plasma, so it could be a memory leak in plasma.
kf.baloo.engine: Running on 32 bit arch, limiting DB mmap to 1 GByte
Why are you running on 32-bit?
:) I know. 32-bit. But I have no option
processor : 3
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS: 144.00
Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4
idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part: 0xd08
CPU revision: 3
>
> So my conclusion is that you're out of memory, most likely due to a
> memory leak somewhere. All the error messages except for the
> kwin_wayland one from plasma, so it could be a memory leak in
> plasma.
I don't know whether it may have something to do with it. I can try it
out later. But I'm maxing out gpu_mem to whatever can be allocated. It's
acceptable though, according to the documentation
Device: llvmpipe (LLVM 13.0.1, 128 bits) (0x)
Video memory: 7893MB
Unified memory: no
GL_AMD_multi_draw_indirect, GL_AMD_pinned_memory,
GL_EXT_framebuffer_object, GL_EXT_framebuffer_sRGB,
GL_EXT_memory_object,
GL_EXT_memory_object_fd, GL_EXT_packed_depth_stencil,
GL_EXT_packed_float,
GL_AMD_pinned_memory, GL_AMD_query_buffer_object,
GL_EXT_gpu_program_parameters, GL_EXT_gpu_shader4,
GL_EXT_memory_object,
GL_EXT_memory_object_fd, GL_EXT_multi_draw_arrays,
GL_EXT_map_buffer_range, GL_EXT_memory_object,
GL_EXT_memory_object_fd,
Re: kwin_wayland: ../libepoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed.
On 5/23/22 16:01, Thiago Macieira wrote: On Monday, 23 May 2022 11:07:35 PDT Carlos wrote: QImage::scaled: Image is a null image This first line probably indicates an out-of-memory condition: some operation prior to this failed to allocate memory for its image, so scaled() simply complained that there was no image to scale. All the other errors after this could be related, like: plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. This could be that it can't get the some information because the image was null. But, looking at the code, it looks more like more memory allocation failure: And this is the additional info I get every time by hovering over the hidden window or session. (you're probably correct). If the same windows or sessions were to be left maximized, or taking up the rest of the screen/display, it doesn't happen. QImage::scaled: Image is a null image qt.qpa.wayland: Wayland does not support QWindow::requestActivate() kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_186(0x9a0aedd8, name="popupWindow") kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_186(0x9a0aedd8, name="popupWindow") kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_186(0x9a0aedd8, name="popupWindow") qt.qpa.wayland: Wayland does not support QWindow::requestActivate() kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_186(0x9a0aedd8, name="popupWindow") kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_186(0x9a0aedd8, name="popupWindow") kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_186(0x9a0aedd8, name="popupWindow") QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0xe556a8) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0xe556a8) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0xe556a8) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0xe556a8) plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. plasma_workspace_pipewire_logging: Failed to query DMA-BUF format count. kwin_wayland: ../libepoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed. Gdk-Message: 17:12:50.470: Error reading events from display: Broken pipe The Wayland connection broke. Did the Wayland compositor die? (EE) failed to read Wayland events: Connection reset by peer The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? kdeinit5: KLauncher died unexpectedly. kdeinit5: preparing to launch '/usr/lib/kf5/klauncher' kdeinit5: Launched KLauncher, pid = 16757, result = 0 kdeinit5: PID 16123 terminated. The X11 connection broke (error 1). Did the X11 server die? The X11 connection broke (error 1). Did the X11 server die? The X11 connection broke (error 1). Did the X11 server die? The X11 connection broke (error 1). Did the X11 server die? kdeinit5: Fatal IO error: client killed kdeinit5: sending SIGHUP to children. kdeinit5: sending SIGTERM to children. kdeinit5: Exit. Exiting due to channel error. Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=20.8803) Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. No backend specified through command line argument, trying auto resolution kf.globalaccel.kglobalacceld: Failed to register service org.kde.kglobalaccel QImage::scaled: Image is a null image libEGL warning: DRI2: failed to authenticate OpenGL vendor string: Mesa/X.org OpenGL renderer string: llvmpipe (LLVM 13.0.1, 128 bits) OpenGL version string: 4.5 (Core Profile) Mesa 22.0.4 OpenGL shading lan
Re: kwin_wayland: ../libepoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed.
On Monday, 23 May 2022 13:42:45 PDT Carlos wrote: > :) I know. 32-bit. But I have no option > > processor : 3 > model name : ARMv7 Processor rev 3 (v7l) > BogoMIPS: 144.00 > Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 > idiva idivt vfpd32 lpae evtstrm crc32 > CPU implementer : 0x41 > CPU architecture: 7 > CPU variant : 0x0 > CPU part: 0xd08 > CPU revision: 3 Are you sure you have enough RAM for the purpose you're trying to use this device for? You should consider either upgrading to something more modern or limiting your use of this old, embedded device. I'd never even heard of armv7l until your email (I only knew of -A, -M and - R). -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel DPG Cloud Engineering
