Fedora 36(Rawhide): easyeffects crashing with OOM situation on 3GB RAM aarch64 Pinephone

[Cyborgscode]

All relevant Informations are here, including a full stacktrace:

https://bugzilla.redhat.com/show_bug.cgi?id=2014451

Excerpt: (full in the link above)

Okt 15 11:26:36 fedorapine easyeffects[1815]: Compositor doesn't support moving popups, relying on remapping
Okt 15 11:26:36 fedorapine easyeffects[1815]: DRM_IOCTL_MODE_CREATE_DUMB failed: Nicht genügend Hauptspeicher verfügbar
Okt 15 11:26:36 fedorapine systemd[1]: Created slice Slice /system/systemd-coredump.
Okt 15 11:26:36 fedorapine systemd[1]: Started Process Core Dump (PID 1854/UID 0).
Okt 15 11:26:37 fedorapine systemd-coredump[1855]: Removed old coredump core.easyeffects.1000.1482333ecd2547829c378dfa83ff8b03.2282.1633635807000000.zst.
Okt 15 11:26:45 fedorapine systemd-coredump[1855]: [🡕] Process 1815 (easyeffects) of user 1000 dumped core.

Stack trace of thread 1815:
#0 0x0000007f8a289ec8 dri2_query_image (sun4i-drm_dri.so + 0x1f0ec8)
#1 0x0000007f9844bc60 create_wl_buffer (libEGL_mesa.so.0 + 0x24c60)
#2 0x0000007f9844c514 dri2_wl_swap_buffers_with_damage (libEGL_mesa.so.0 + 0x25514)
#3 0x0000007f98442510 dri2_swap_buffers_with_damage (libEGL_mesa.so.0 + 0x1b510)
#4 0x0000007f98432ac0 _eglSwapBuffersWithDamageCommon (libEGL_mesa.so.0 + 0xbac0)
#5 0x0000007fb62eae84 gdk_wayland_gl_context_end_frame (libgtk-4.so.1 + 0x401e84)
#6 0x0000007fb62b872c gdk_draw_context_end_frame (libgtk-4.so.1 + 0x3cf72c)
#7 0x0000007fb633fd28 gsk_ngl_renderer_render (libgtk-4.so.1 + 0x456d28)
#8 0x0000007fb6319f9c gsk_renderer_render (libgtk-4.so.1 + 0x430f9c)
#9 0x0000007fb61dedc4 gtk_widget_render (libgtk-4.so.1 + 0x2f5dc4)
#10 0x0000007fb61dfb08 surface_render (libgtk-4.so.1 + 0x2f6b08)
#11 0x0000007fb62a6ef8 _gdk_marshal_BOOLEAN__BOXEDv (libgtk-4.so.1 + 0x3bdef8)
#12 0x0000007fb6718df0 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33df0)
#13 0x0000007fb6718f80 g_signal_emit (libgobject-2.0.so.0 + 0x33f80)
#14 0x0000007fb62ce304 gdk_surface_paint_on_clock (libgtk-4.so.1 + 0x3e5304)
#15 0x0000007fb66f8998 g_closure_invoke (libgobject-2.0.so.0 + 0x13998)
#16 0x0000007fb672659c signal_emit_unlocked_R.isra.0 (libgobject-2.0.so.0 + 0x4159c)
#17 0x0000007fb6718cb0 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33cb0)
#18 0x0000007fb6718f80 g_signal_emit (libgobject-2.0.so.0 + 0x33f80)
#19 0x0000007fb62c4740 gdk_frame_clock_paint_idle (libgtk-4.so.1 + 0x3db740)
#20 0x0000007fb684035c g_timeout_dispatch (libglib-2.0.so.0 + 0x5835c)
#21 0x0000007fb683fac0 g_main_context_dispatch (libglib-2.0.so.0 + 0x57ac0)
#22 0x0000007fb6898120 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xb0120)
#23 0x0000007fb683cd3c g_main_context_iteration (libglib-2.0.so.0 + 0x54d3c)
#24 0x0000007fb5dc7688 g_application_run (libgio-2.0.so.0 + 0xf1688)
#25 0x0000005592cb6694 main (easyeffects + 0x56694)
#26 0x0000007fb4c800c4 __libc_start_call_main (libc.so.6 + 0x2b0c4)
#27 0x0000007fb4c80198 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2b198)
#28 0x0000005592cb7bf0 _start (easyeffects + 0x57bf0)

[Cyborgscode]

"nicht genügend Hauptspeicher verfügbar" =>" not enough memory available "

[wwmm]

I do not have a way to test this on ARM yet. But based on some of the errors I think that gtk4 is having problems with the video driver and the desktop compositor

Compositor doesn't support moving popups, relying on remapping
DRM_IOCTL_MODE_CREATE_DUMB failed

The message about the compositor should not be causing the crash. People using gtk4 on Sway also see them. There are other problems the compositor incompatibility causes but not a crash. So the reason must be the out of memory error. DRM messages are related to the gpu. So my guess is that gtk4 is asking for more gpu memory than this device has. OR gtk4 gpu backend is having some kind of incompatibility with this device graphics stack.

[Cyborgscode]

As it's Fedroa Rawhide, the Bleeding Edge of Softwareversions, it can be anything inside MESA or phosh.

So you think, we should include the mesa team on this?

[wwmm]

So you think, we should include the mesa team on this?

I think the first thing to do is contacting gtk developers about the gtk4 state of the support on arm platforms. At this moment gtk4 backend for X11 has some problems. If that one is not perfect I would not be surprised if whatever they are using for ARM has problems too.

[Cyborgscode]

Pinephones are using Wayland .

[wwmm]

Pinephones are using Wayland .

Ok. In this case it may make sense to contact Mesa developers about the crash on dri2_query_image (sun4i-drm_dri.so + 0x1f0ec8). Based on the Stack trace it seems to be the place Mesa developers should be investigating.