Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[TRACKER] GPU rendering issues / app crashes #72

Open
28 of 36 tasks
asahilina opened this issue Dec 7, 2022 · 285 comments
Open
28 of 36 tasks

[TRACKER] GPU rendering issues / app crashes #72

asahilina opened this issue Dec 7, 2022 · 285 comments
Assignees
@asahilina

Comments

@asahilina
Copy link
Member

asahilina commented Dec 7, 2022 •
edited
Loading

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

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)
@asahilina asahilina self-assigned this Dec 7, 2022
@asahilina asahilina mentioned this issue Dec 7, 2022
Open
@BarisUlas

This comment was marked as off-topic.

Sign in to view
@Chainfire

This comment was marked as resolved.

Sign in to view
@aykevl

This comment was marked as resolved.

Sign in to view
@TheBrinkOfTomorrow

This comment was marked as resolved.

Sign in to view
@mkurz

This comment was marked as duplicate.

Sign in to view
@erenatas

This comment was marked as off-topic.

Sign in to view
@jannau

This comment was marked as off-topic.

Sign in to view
@fredlahde

This comment was marked as resolved.

Sign in to view
@BarisUlas

This comment was marked as off-topic.

Sign in to view
@marcan
Copy link
Member

marcan commented Dec 9, 2022 •
edited by asahilina
Loading

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

This comment was marked as resolved.

Sign in to view
@asahilina

This comment was marked as resolved.

Sign in to view
@asahilina
Copy link
Member Author

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

@iaguis

This comment was marked as resolved.

Sign in to view
@fredlahde

This comment was marked as resolved.

Sign in to view
@fredlahde

This comment was marked as resolved.

Sign in to view
@TellowKrinkle

This comment was marked as resolved.

Sign in to view
@Nnubes256

This comment was marked as resolved.

Sign in to view
@marcan marcan mentioned this issue Dec 10, 2022
Closed
@Capta1nT0ad

This comment was marked as resolved.

Sign in to view
@marcan

This comment was marked as resolved.

Sign in to view
@levihuayuzhang

This comment was marked as resolved.

Sign in to view
@aykevl

This comment was marked as resolved.

Sign in to view
@asahilina

This comment was marked as resolved.

Sign in to view
@asahilina

This comment was marked as resolved.

Sign in to view
@aykevl

This comment was marked as resolved.

Sign in to view
@asahilina

This comment was marked as resolved.

Sign in to view
@asahilina

This comment was marked as resolved.

Sign in to view
@alyssarosenzweig

This comment was marked as resolved.

Sign in to view
@alyssarosenzweig

This comment was marked as resolved.

Sign in to view
@nsklaus

This comment was marked as off-topic.

Sign in to view
@alyssarosenzweig

This comment was marked as off-topic.

Sign in to view
@nsklaus

This comment was marked as outdated.

Sign in to view
@alyssarosenzweig

This comment was marked as outdated.

Sign in to view
@nsklaus

This comment was marked as outdated.

Sign in to view
@akihikodaki
Copy link

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
Copy link

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.

@rowanG077 rowanG077 mentioned this issue Aug 5, 2024
Open
@Zirro
Copy link

Zirro commented Sep 17, 2024

I've been seeing a brief flash of magenta when opening menus from the KDE taskbar. It looks like this:

plasma_magenta_glitch2

I've tried running plasma shell with the environment variables from the original post with the same result. This would suggest that it's an issue in Plasma itself, but I would like to confirm here that I'm not alone in seeing the issue given how prominent it would seem to be.

Oh, and Lina, if you're planning to resume development streams any time soon I would be happy to watch you investigate this live 🙂

asahi-diagnose-20240917-165604.txt

@ChristiaanDev

This comment was marked as resolved.

Sign in to view
@TomKeddie

This comment was marked as resolved.

Sign in to view
@filahf

This comment was marked as resolved.

Sign in to view
@asahilina

This comment was marked as resolved.

Sign in to view
@asahilina

This comment was marked as resolved.

Sign in to view
@jannau jannau mentioned this issue Oct 22, 2024
Open
@asahilina
Copy link
Member Author

Both the shadertoy thing and the emacs regression are fixed in 24.3.0-asahi20241104 (will be pushed to the repos soon).

@mkurz

This comment was marked as resolved.

Sign in to view
@mkurz

This comment was marked as resolved.

Sign in to view
@mkurz mkurz mentioned this issue Nov 4, 2024
Merged
@asahilina

This comment was marked as resolved.

Sign in to view
@asahilina

This comment was marked as resolved.

Sign in to view
@mkurz

This comment was marked as resolved.

Sign in to view
@mkurz

This comment was marked as resolved.

Sign in to view
@asahilina

This comment was marked as resolved.

Sign in to view
@Zirro
Copy link

Zirro commented Nov 5, 2024 •
edited
Loading

...so this looks like a KWin bug (not supporting the X11 SHAPE extension properly).

Looks like there might have been an intentional change regarding this in 6.2: https://invent.kde.org/plasma/kwin/-/merge_requests/6247. It does seem a bit unfortunate to lose such a capability even if it mainly concerns xeyes.

EDIT: Update - It's coming back since it was found to be used by Wine as well:
https://invent.kde.org/plasma/kwin/-/merge_requests/6779

@mkurz mkurz mentioned this issue Nov 6, 2024
Open
@asahilina
Copy link
Member Author

asahilina commented Nov 9, 2024 •
edited
Loading

New issue: GTK4 apps have visual corruption when using noninteger scales on Wayland. I believe this is a GTK4 bug, not a driver bug (it fails to properly clear a buffer, leading to undefined behavior). It started happening recently because KWin now supports fractional scaling on Wayland, but it is not a regression.

Edit: Filed here: https://gitlab.gnome.org/GNOME/gtk/-/issues/7146

@mkurz
Copy link

mkurz commented Nov 9, 2024

@asahilina I think following two bugs in your list above can be marked as resolved(?):

  • Google Maps on Firefox is slow/jerky
  • Moving the mouse above blurred backgrounds in KWin/Wayland causes artifacts (upstream bug)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@asahilina asahilina

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests