[TRACKER] GPU rendering issues / app crashes

[hoshinolina]

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
• xeyes has a magenta/nontransparent background in kwin and wlroots compositors (they do not implement X11 SHAPE, see wlroots issue; GNOME/mutter works).
• GTK4 apps have visual corruption with non-integer scales (GTK4 bug, patched in Fedora)
• Faults and mipmap-related artifacts in GTK4 apps (GTK4 bug, worked around in Fedora Asahi Remix with GSK_RENDERER=ngl)

[BarisUlas]

I'm not really sure which category this issue belongs to, but I'm having problems running Wayland with the newly installed linux-asahi-edge and mesa-asahi-edge. I followed the guide precisely, but when I try to login to Wayland, it goes to a blank black screen for about 5 seconds, then puts me back into the login screen where I can choose X11 or Wayland to login with. The issue does not occur with X11. Here's the output of asahi-diagnose. Let me know if you need anything else!

asahi-diagnose-20221207-110359.txt

[Chainfire]

I don't get GUI at all after installing asahi-edge and mesa-asahi-edge. Split-second black screen with cursor, and back to text mode. MBP M1 Max, nothing at all connected but a USB ethernet dongle. asahi-diagnose output attached.

asahi-diagnose-20221207-090233.txt

EDIT: solved by pacman -S asahi-desktop-meta, thanks to jannau. Apparently I have an old install :)

[aykevl]

The system monitor applets are glitchy when set to "Line Chart". I think all of them, but at least the Memory Usage widget. It doesn't draw the line chart, but instead it draws over other apps (about 1/3 the screen width).
It also seems to happen with "Grid", but not with the other display styles.

This happens in both Xorg and Wayland. (Using Xorg still because I can't seem to get scaling to work well on Wayland).

asahi-diagnose-20221207-125011.txt

Update: unfortunately the recent mesa update didn't fix this (I hoped it would). Also, I can confirm the System Monitor program has the same issue, as reported by @TheBrinkOfTomorrow. I did find that LIBGL_ALWAYS_SOFTWARE=1 plasma-systemmonitor works around this issue.

Update 2: the latest mesa update also fixed the issue with the system monitor applets in the Plasma panel!

[TheBrinkOfTomorrow]

The system monitor applets are glitchy when set to "Line Chart". I think all of them, but at least the Memory Usage widget. It doesn't draw the line chart, but instead it draws over other apps (about 1/3 the screen width). It also seems to happen with "Grid", but not with the other display styles.

Same issue for me (using Wayland). Graphics corruption is restricted to the internal boundaries of the System Monitor view.
asahi-diagnose-20221207-080358.txt

[mkurz]

Same issue with the system monitor like described in the two comments above here too. The applets in the taskbar don't work correctly and the history tab inside the app has the same/similar glitches like in the above screenshot.
Using a Macbook Pro 14" 10‑Core CPU 16‑Core GPU, 16‑Core Neural Engine, 32 GB RAM.
Asahi is up to date, containing yesterday's mesa fixes.

[erenatas]

Followed the steps on the blog as described, I cannot get to Plasma session on Wayland. I see terminal cursor blinking fast, then back to SDDM.
asahi-diagnose-20221208-204440.txt

[jannau]

Followed the steps on the blog as described, I cannot get to Plasma session on Wayland. I see terminal cursor blinking fast, then back to SDDM. asahi-diagnose-20221208-204440.txt

dec 08 20:30:24 eatasbkng kernel: asahi 206400000.gpu: Unsupported GPU/firmware combination (G13, [12, 4, 0])

You have used macOS 12.4 as stub/firmware version on a M1 device. This is not supported. The 12.4 GPU firmware is only supported on M2 devices since those were released with 12.4.

[fredlahde]

I've got an issue in firefox 107.0.1 when browsing Plex on wayland, together wih gpu timeouts.

This is what it should look like (linux-asahi, X11):
https://github.com/fredlahde/asahi-gpu-bug-report/raw/main/plex/Screenshot%202022-12-08%20at%2020-51-14%20Eminem%20-%20Seduction.png

This is what it actually looks like (linux-asahi-edge, Wayland):
https://github.com/fredlahde/asahi-gpu-bug-report/raw/main/plex/Screenshot%202022-12-08%20at%2020-47-30%20Eminem%20-%20Seduction.png

Diagnose File:
https://raw.githubusercontent.com/fredlahde/asahi-gpu-bug-report/main/plex/asahi-diagnose-20221208-204618.txt

[BarisUlas]

@jannau do you know how to work around the stub version caused issues? I'm also having an issue where wayland just refuses to work and the only thing I see is a blinking cursor, then the lockscreen again. You can also find my asahi-diagnose log here

[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.

[hoshinolina]

The System Monitor issues should now be fixed! ✨

[hoshinolina]

@fredlahde Can you update, reboot and test the Firefox/Plex thing again? I don't have a Plex server to test with...

[hoshinolina]

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 ^^