[TRACKER] GPU rendering issues / app crashes

[asahilina]

This is a tracker bug for general GPU issues, like:

• Apps that crash after startup
• Rendering glitches
• GPU fault/timeout errors

When making a comment on this bug, please run the asahi-diagnose command and attach the file it saves to your comment. Please tell us what you were doing when the problem happened, what desktop environment and window system you use, and any other details about the issue.

The purpose of this bug is to collect reports of app issues in one place, so we have somewhere to look when figuring out what to work on. Since the driver is still a work-in-progress and lots of things are not expected to work, please don't expect a timely response to reports. We're working on it!

Before reporting something, please check that the issue has not been reported already. Duplicate reports just clutter up the bug and will be marked as duplicate. --marcan

• If you are having shader errors with Chromium/Electron-based apps after an update, delete your shader cache: rm -rf ~/.config/chromium/Default/GPUCache (or similar paths for other apps). Upstream bug. This is not a driver bug.

• If you run into a GPU lockup or crash (all GPU apps stop working, but you can still SSH into the machine), please open a new bug in this repo, tell us what you were doing when the GPU locked up, and attach the asahi-diagnose log.

• If you get GPU fault or GPU timeout messages in dmesg (probably together with rendering issues), but the GPU keeps working in general, this tracker bug is the right place to report that.

• If you have linux-asahi-edge issues unrelated to the GPU, please report them here. This includes display output/controller related issues, like screen resolution switching and backlight control, which are unrelated to the GPU driver.

• If you are seeing single-pixel-wide glitches, please set your screen scale to 100%, log out and back in, and try to reproduce it again. These kinds of glitches are likely to be compositor/desktop environment bugs related to fractional scaling, rather than driver issues.

If you see magenta

Magenta is the error color on Apple GPUs. It is what you get when you sample an uninitialized compressed texture. This often happens with driver bugs that break rendering, but there are also many apps that have bugs that transiently display uninitialized buffer contents. These will often show up as black or transparent on other GPUs or with software rendering, which stands out less but it indicates the same bug.

If you see magenta glitches, please try running the app with ASAHI_MESA_DEBUG=nocompress. If you see the same problems but they are now black, try LIBGL_ALWAYS_SOFTWARE=true to force software rendering. If you get the same results (still black regions where previously there was magenta), then it is likely an app bug or an upstream Mesa bug, not a driver issue.

Another common issue is apps that have rendering feedback loops, which are undefined behavior in OpenGL. These often result in 4x2 pixel shaped corruption regions. You can work around this with ASAHI_MESA_DEBUG=nocompress, which should fix the issue (at least if it wouldn't normally break on all GPUs). This could also be caused by a driver bug, though, so please do report anything that is fixed with nocompress so we can take a look and determine whether it's an app bug or a driver bug!

Known issues

• When GPU timeouts/faults occur, rarely the firmware can lock up (see [GPU Lockup] Rare firmware robustness issues while recovering from faults #79)
• Google Maps on Firefox is slow/jerky

Resolved issues

• System Monitor glitches in the History tab
• Plasmashell sometimes shows magenta areas or missing rendering
• Portraits render incorrectly or cause faults in Darwinia
• Geometry edges render poorly/jagged in Darwinia
• WebGL Aquarium faults above 10000 fish
• Xorg sometimes flashes black while switching windows in KWin
• gl_FragDepth is not implemented
• three.js scenes (and other complex renders) with MSAA glitch on Pro/Max/Ultra machines
• Discard regressed with the OpenGL 3.1 update (breaking Darwinia)
• MSRTT wrongly advertised when not properly supported (making Darwinia MSAA not work)
• Texture barriers wrongly advertised when not properly supported (X11/Emacs glitching)
• Water glitches near screen edges in Darwinia if you get up really close.
• (6.2/explicit sync regression) KWin flashes magenta rectangles when starting up, or right before going to sleep.
• Nautilus is pink with Adwaita
• Google Maps & PDF viewer on Firefox use too much memory
• Corrupted X11 apps on GNOME/XWayland
• Rendering with some render targets disabled regressed (Inochi2D, KiCad 3D glitching)
• Figma rendering is glitchy
• CSS transforms in Firefox render incorrectly
• Complex GTK apps (GIMP, etc.) under XWayland sometimes glitch magenta
• Register spilling is excessively slow (example)

Issues that aren't driver bugs

• gnome-terminal has a glitchy background (upstream bug from 2 years ago, they don't seem interested in fixing it...)
• Moving the mouse above blurred backgrounds in KWin/Wayland causes artifacts (upstream bug)
• KWin has single-pixel glitches when fractional scaling is enabled (Fixed in plasma 5.27.7)
• OBS screen sharing does not work (PipeWire regression, fixed in 0.3.62, plus KWin bug (merged for 5.26.5, ETA Jan 3), plus core Mesa bug)
• Some WebGL apps on Firefox (like Plex and QuakeJS) can hang/fail to render (upstream bug, fixed for Firefox 110)
• Firefox sometimes flashes magenta on startup (upstream bug)
• SuperTuxKart sometimes has rectangular black glitches (upstream bug) (worked around in driver for now)
• QuakeJS has jittery geometry (emscripten bug, fixed years ago but they need to update). Probably applies to any WebGL apps with similar issues too.
• Window corruption / magenta regions with Java OpenGL rendering enabled (Java does not double buffer its OpenGL visual so it will always tear/break on any modern system from this decade, just worse on Apple with compression.)
• Google Sheets gets blurry on scroll (Google Sheets bug Firefox bug) (workaround: ASAHI_MESA_DEBUG=no16)
• blender's gl version check is sketchy https://bugzilla.redhat.com/show_bug.cgi?id=2237821

[marcan]

Please do not add "me too" comments, as they just clutter everything up. Once an issue is reported, it's enough, we don't need more reports (unless you're going to add useful info, like more detailed/reliable repro steps --Lina).

Please don't report issues with nonstandard unsupported firmware. If you picked expert mode in the installer and then chose the wrong non-default options, you're on your own. You'll have to reinstall to fix it. It's called expert mode for a reason - if you break it you get to keep the pieces.

[asahilina]

I noticed that GitHub is showing comments we mark as resolved as simply "hidden". We're just hiding them to declutter the bug, don't worry! Please look for that wording (This comment has been hidden.) if you're looking for previous comments reporting issues that have since been fixed ^^

[SamilKaraduman]

Chromium glitches and becomes unresponsive while trying to install an extension (or it freezes the whole UI)

System details

OS: Fedora Linux Asahi Remix 39 (Thirty Nine) aarch64 Host: Apple MacBook Pro (13-inch, M1, 2020) Kernel: 6.6.3-413.asahi.fc39.aarch64+16k Resolution: 2560x1600 DE: Plasma 5.27.10 WM: kwin Theme: [Plasma], Breeze [GTK2/3] Icons: [Plasma], breeze [GTK2/3] CPU: (8) @ 2.064GHz Memory: 4588MiB / 7458MiB

asahi-diagnose-20240202-025755.txt

Problem description

After installing Chromium through: sudo dnf install chromium I set its window to fullscreen, then headed to the "Chrome web store" to install "uBlock Origin" and as soon as I clicked "Add to Chrome" the whole window became unresponsive and started glitching, as shown below:
2024-02-02.02-24-20.mp4

Note: everything freezes instead when I try to reproduce these steps with the window restored down, not fullscreen. I was forced to manually turn off the MacBook by holding the power button down.

I can always reproduce the issue, even after rebooting or executing: rm -rf ~/.config/chromium/Default/GPUCache. The behavior keeps being the same.

For me, the only way to fix this issue is to run Chromium through Wayland using chrome://flags and searching "ozone," then enabling auto in the preferred ozone platform.

[alyssarosenzweig]

When attempting to run Demon’s Souls on rpcs3 (compiled locally from the git repo, version 0.0.30-16122-7abc5f3e), the game fails to boot. This is the log output: RPCS3 Asahi OpenGL Demons Souls.log

F {RSX [0x0000000]} SIG: Thread terminated due to fatal error: Could not bind OpenGL context
(in file /home/snow/software/rpcs3-files2/rpcs3/rpcs3/rpcs3qt/gl_gs_frame.cpp:89[:4], in function set_current) (errno=25=Inappropriate ioctl for device)

The game can launch into the start menu when using Vulkan as the renderer and llvmpipe as the graphical device, so it shows that games can boot but something with OpenGL isn’t working properly.

My DE is the default KDE that installs with Asahi on Fedora. I’m using a 14" M1 Pro Max with 10 cores. This is the output for asahi-diagnose: asahi-diagnose-20240217-154410.txt

This isn't really actionable. Hopefully the rpcs3 devs can help you.

[alyssarosenzweig]

Hello, I have been enjoying Fedora (Asahi Remix) have ran into an (what I think has not been reported yet) GPU-rendering issue.

For context: I have an M1 Pro 10 core 14" Macbook Pro 2021, running Fedora (Asahi Remix) with the latest updates. I use SwayFX (Sway fork) with Waybar.

So I play Old School RuneScape using a third-party client, called HDOS. This uses OpenGL and I thought I'd give it a shot after the last update.

However, it seems to get a lot of corruption in combination with a lot of GPU timeouts so I wanted to report that. It's not consistently getting corrupted so it seems to be really close to be able to render it out perfectly.

Example of it being perfect one frame:

Example of it corrupting on a frame:

Log file (obtained by using dmesg --follow-new > dmesg-hdos-logs-16-02-2024.log: dmesg-hdos-logs-16-02-2024.log

asahi-diagnose output file: asahi-diagnose-20240216-121914.txt

For debugging, you do not need an account to try it out; you can just execute the jar file and the corruption will show up on menu in front of the login screen.

I hope this is the right place to report this issue.

Thanks!

Update: spelling errors, uploaded the wrong file so now just added both the asahi-diagnose file, as well as the specific dmesg log file.

Please capture an apitrace, ensure it shows the problem when replaying, and attach. Thanks

[ChristiaanDev]

Hello, I have been enjoying Fedora (Asahi Remix) have ran into an (what I think has not been reported yet) GPU-rendering issue.
For context: I have an M1 Pro 10 core 14" Macbook Pro 2021, running Fedora (Asahi Remix) with the latest updates. I use SwayFX (Sway fork) with Waybar.
So I play Old School RuneScape using a third-party client, called HDOS. This uses OpenGL and I thought I'd give it a shot after the last update.
However, it seems to get a lot of corruption in combination with a lot of GPU timeouts so I wanted to report that. It's not consistently getting corrupted so it seems to be really close to be able to render it out perfectly.
Example of it being perfect one frame:
Example of it corrupting on a frame:
Log file (obtained by using dmesg --follow-new > dmesg-hdos-logs-16-02-2024.log: dmesg-hdos-logs-16-02-2024.log
asahi-diagnose output file: asahi-diagnose-20240216-121914.txt
For debugging, you do not need an account to try it out; you can just execute the jar file and the corruption will show up on menu in front of the login screen.
I hope this is the right place to report this issue.
Thanks!
Update: spelling errors, uploaded the wrong file so now just added both the asahi-diagnose file, as well as the specific dmesg log file.

Please capture an apitrace, ensure it shows the problem when replaying, and attach. Thanks

I have uploaded it on my homeserver as it's quite a large dump and the maximum size is 25MB.
https://dumps.christiaan.dev/java.trace

I hope I dumped it properly, when replaying I indeed get an error:

Let me know if you need some more information.
Thank you.

[nsklaus]

was there any reports on ryujinx yet ?
i have a bunch of switch games, should i continue reporting on those ?

here's red dead redemption, right at the beginning, in the train station.
speed feels like 5fps, there are blinking textures and dark squares, in the nearby scenery, and on the horizon the outline of objects appear block-ish. it looks like some shadow and alpha channel problems.

for reference, here's the pc version:

[nsklaus]

you mean they would have a black texture bug that manifest itself specifically on linux arm64 but not on linux x86_64 ? you wouldn't remember the issue or PR referencing it, so i could follow its progress or eventually add to it ?

[alyssarosenzweig]

you mean they would have a black texture bug that manifest itself specifically on linux arm64 but not on linux x86_64 ? you wouldn't remember the issue or PR referencing it, so i could follow its progress or eventually add to it ?

It was discussed on the ryujinx discord last week.

[nsklaus]

i see, so no issue no PR created for it yet ? that would explain why i didn't find much at a quick glance over their repo. maybe i'll create a report there myself then. thanks for telling.

[akihikodaki]

I observed crashes with Zoom on Firefox. The frequency of crashes is once in tens of minutes. Unfortunately it doesn't generate core dumps. Here is the output of journalctl -t firefox.desktop -b:

 4月 08 09:49:43 fedora firefox.desktop[3957]: [Child 3957, MediaDecoderStateMachine #1] WARNING: Decoder=aaab64841b90 Decode error: NS_ERROR_DOM_MEDIA_DECODE_ERR (0x806e0004) - virtual mozilla::MediaResult mozilla::FFmpegVideoDecoder<60>::DoDecode(mozilla::MediaRawData*, uint8_t*, int, bool*, mozilla::MediaDataDecoder::DecodedData&): avcodec_send_packet error: Unknown error occurred: file /builddir/build/BUILD/firefox-124.0.1/dom/media/MediaDecoderStateMachineBase.cpp:166
 4月 08 09:49:46 fedora firefox.desktop[3957]: [Child 3957, MediaDecoderStateMachine #1] WARNING: Decoder=aaab64841b90 Decode error: NS_ERROR_DOM_MEDIA_DECODE_ERR (0x806e0004) - virtual mozilla::MediaResult mozilla::FFmpegVideoDecoder<60>::DoDecode(mozilla::MediaRawData*, uint8_t*, int, bool*, mozilla::MediaDataDecoder::DecodedData&): avcodec_send_packet error: Unknown error occurred: file /builddir/build/BUILD/firefox-124.0.1/dom/media/MediaDecoderStateMachineBase.cpp:166
 4月 08 10:50:44 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) [GFX1]: DMABuf surface import failed!
 4月 08 10:50:44 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) [GFX1-]: TextureHost creation failure type=4
 4月 08 10:50:44 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) [GFX1-]: Failed to create remote texture
 4月 08 10:50:44 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) [GFX1]: DMABuf surface import failed!
 4月 08 10:50:44 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) |[4][GFX1-]: TextureHost creation failure type=4 (t=3775.53) [GFX1-]: TextureHost creation failure type=4
 4月 08 10:50:44 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) |[4][GFX1-]: TextureHost creation failure type=4 (t=3775.53) |[5][GFX1]: DMABuf surface import failed! (t=3775.58) [GFX1]: DMABuf surface import failed!
 4月 08 10:50:44 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) |[4][GFX1-]: TextureHost creation failure type=4 (t=3775.53) |[5][GFX1]: DMABuf surface import failed! (t=3775.58) |[6][GFX1-]: TextureHost creation failure type=4 (t=3775.58) [GFX1-]: TextureHost creation failure type=4
 4月 08 10:50:44 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) |[4][GFX1-]: TextureHost creation failure type=4 (t=3775.53) |[5][GFX1]: DMABuf surface import failed! (t=3775.58) |[6][GFX1-]: TextureHost creation failure type=4 (t=3775.58) |[7][GFX1]: DMABuf surface import failed! (t=3775.65) [GFX1]: DMABuf surface import failed!
 4月 08 10:50:44 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) |[4][GFX1-]: TextureHost creation failure type=4 (t=3775.53) |[5][GFX1]: DMABuf surface import failed! (t=3775.58) |[6][GFX1-]: TextureHost creation failure type=4 (t=3775.58) |[7][GFX1]: DMABuf surface import failed! (t=3775.65) |[8][GFX1-]: TextureHost creation failure type=4 (t=3775.65) [GFX1-]: TextureHost creation failure type=4
 4月 08 10:50:44 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) |[4][GFX1-]: TextureHost creation failure type=4 (t=3775.53) |[5][GFX1]: DMABuf surface import failed! (t=3775.58) |[6][GFX1-]: TextureHost creation failure type=4 (t=3775.58) |[7][GFX1]: DMABuf surface import failed! (t=3775.65) |[8][GFX1-]: TextureHost creation failure type=4 (t=3775.65) |[9][GFX1]: DMABuf surface import failed! (t=3775.71) [GFX1]: DMABuf surface import failed!
 4月 08 10:50:44 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) |[4][GFX1-]: TextureHost creation failure type=4 (t=3775.53) |[5][GFX1]: DMABuf surface import failed! (t=3775.58) |[6][GFX1-]: TextureHost creation failure type=4 (t=3775.58) |[7][GFX1]: DMABuf surface import failed! (t=3775.65) |[8][GFX1-]: TextureHost creation failure type=4 (t=3775.65) |[9][GFX1]: DMABuf surface import failed! (t=3775.71) |[10][GFX1-]: TextureHost creation failure type=4 (t=3775.71) [GFX1-]: TextureHost creation failure type=4
 4月 08 10:50:44 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) |[4][GFX1-]: TextureHost creation failure type=4 (t=3775.53) |[5][GFX1]: DMABuf surface import failed! (t=3775.58) |[6][GFX1-]: TextureHost creation failure type=4 (t=3775.58) |[7][GFX1]: DMABuf surface import failed! (t=3775.65) |[8][GFX1-]: TextureHost creation failure type=4 (t=3775.65) |[9][GFX1]: DMABuf surface import failed! (t=3775.71) |[10][GFX1-]: TextureHost creation failure type=4 (t=3775.71) |[11][GFX1]: DMABuf surface import failed! (t=3775.76) [GFX1]: DMABuf surface import failed!
 4月 08 10:50:44 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) |[4][GFX1-]: TextureHost creation failure type=4 (t=3775.53) |[5][GFX1]: DMABuf surface import failed! (t=3775.58) |[6][GFX1-]: TextureHost creation failure type=4 (t=3775.58) |[7][GFX1]: DMABuf surface import failed! (t=3775.65) |[8][GFX1-]: TextureHost creation failure type=4 (t=3775.65) |[9][GFX1]: DMABuf surface import failed! (t=3775.71) |[10][GFX1-]: TextureHost creation failure type=4 (t=3775.71) |[11][GFX1]: DMABuf surface import failed! (t=3775.76) |[12][GFX1-]: TextureHost creation failure type=4 (t=3775.76) [GFX1-]: TextureHost creation failure type=4
 4月 08 10:50:44 fedora firefox.desktop[2807]: [Parent 2807, IPC I/O Parent] WARNING: Message needs unreceived descriptors channel:ffff5407ab80 message-type:11403270 header()->num_handles:1 num_fds:0 fds_i:0: file /builddir/build/BUILD/firefox-124.0.1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc:467
 4月 08 10:50:44 fedora firefox.desktop[8414]: Exiting due to channel error.
 4月 08 10:53:21 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) |[4][GFX1-]: TextureHost creation failure type=4 (t=3775.53) |[5][GFX1]: DMABuf surface import failed! (t=3775.58) |[6][GFX1-]: TextureHost creation failure type=4 (t=3775.58) |[7][GFX1]: DMABuf surface import failed! (t=3775.65) |[8][GFX1-]: TextureHost creation failure type=4 (t=3775.65) |[9][GFX1]: DMABuf surface import failed! (t=3775.71) |[10][GFX1-]: TextureHost creation failure type=4 (t=3775.71) |[11][GFX1]: DMABuf surface import failed! (t=3775.76) |[12][GFX1-]: TextureHost creation failure type=4 (t=3775.76) |[13][GFX1]: DMABuf surface import failed! (t=3932.42) [GFX1]: DMABuf surface import failed!
 4月 08 10:53:21 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) |[4][GFX1-]: TextureHost creation failure type=4 (t=3775.53) |[5][GFX1]: DMABuf surface import failed! (t=3775.58) |[6][GFX1-]: TextureHost creation failure type=4 (t=3775.58) |[7][GFX1]: DMABuf surface import failed! (t=3775.65) |[8][GFX1-]: TextureHost creation failure type=4 (t=3775.65) |[9][GFX1]: DMABuf surface import failed! (t=3775.71) |[10][GFX1-]: TextureHost creation failure type=4 (t=3775.71) |[11][GFX1]: DMABuf surface import failed! (t=3775.76) |[12][GFX1-]: TextureHost creation failure type=4 (t=3775.76) |[13][GFX1]: DMABuf surface import failed! (t=3932.42) |[14][GFX1-]: TextureHost creation failure type=4 (t=3932.42) [GFX1-]: TextureHost creation failure type=4
 4月 08 10:53:21 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[1][GFX1-]: TextureHost creation failure type=4 (t=3775.46) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) |[4][GFX1-]: TextureHost creation failure type=4 (t=3775.53) |[5][GFX1]: DMABuf surface import failed! (t=3775.58) |[6][GFX1-]: TextureHost creation failure type=4 (t=3775.58) |[7][GFX1]: DMABuf surface import failed! (t=3775.65) |[8][GFX1-]: TextureHost creation failure type=4 (t=3775.65) |[9][GFX1]: DMABuf surface import failed! (t=3775.71) |[10][GFX1-]: TextureHost creation failure type=4 (t=3775.71) |[11][GFX1]: DMABuf surface import failed! (t=3775.76) |[12][GFX1-]: TextureHost creation failure type=4 (t=3775.76) |[13][GFX1]: DMABuf surface import failed! (t=3932.42) |[14][GFX1-]: TextureHost creation failure type=4 (t=3932.42) |[15][GFX1]: DMABuf surface import failed! (t=3932.48) [GFX1]: DMABuf surface import failed!
 4月 08 10:53:21 fedora firefox.desktop[2807]: Crash Annotation GraphicsCriticalError: |[0][GFX1]: DMABuf surface import failed! (t=3775.46) |[16][GFX1-]: TextureHost creation failure type=4 (t=3932.48) |[2][GFX1-]: Failed to create remote texture (t=3775.46) |[3][GFX1]: DMABuf surface import failed! (t=3775.53) |[4][GFX1-]: TextureHost creation failure type=4 (t=3775.53) |[5][GFX1]: DMABuf surface import failed! (t=3775.58) |[6][GFX1-]: TextureHost creation failure type=4 (t=3775.58) |[7][GFX1]: DMABuf surface import failed! (t=3775.65) |[8][GFX1-]: TextureHost creation failure type=4 (t=3775.65) |[9][GFX1]: DMABuf surface import failed! (t=3775.71) |[10][GFX1-]: TextureHost creation failure type=4 (t=3775.71) |[11][GFX1]: DMABuf surface import failed! (t=3775.76) |[12][GFX1-]: TextureHost creation failure type=4 (t=3775.76) |[13][GFX1]: DMABuf surface import failed! (t=3932.42) |[14][GFX1-]: TextureHost creation failure type=4 (t=3932.42) |[15][GFX1]: DMABuf surface import failed! (t=3932.48) [GFX1-]: TextureHost creation failure type=4
 4月 08 10:53:21 fedora firefox.desktop[2807]: [Parent 2807, IPC I/O Parent] WARNING: Message needs unreceived descriptors channel:ffff54351910 message-type:11403270 header()->num_handles:1 num_fds:0 fds_i:0: file /builddir/build/BUILD/firefox-124.0.1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc:467
 4月 08 10:53:21 fedora firefox.desktop[12322]: Exiting due to channel error.

[akihikodaki]

I logged with Dmabuf:5 logging configuration: https://firefox-source-docs.mozilla.org/xpcom/logging.html
log.txt-main.2807.moz_log.log
The log is localized in Japanese and says "ファイルを開きすぎです", which means "Too many open files". The log shows Firefox imported many DMA-BUF without releasing them. Perhaps it is just a Firefox bug.