-
Notifications
You must be signed in to change notification settings - Fork 92
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.
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
[TRACKER] GPU rendering issues / app crashes #72
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
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. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
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 ^^ |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
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
|
I logged with |
I've been seeing a brief flash of magenta when opening menus from the KDE taskbar. It looks like this: 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 🙂 |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Both the shadertoy thing and the emacs regression are fixed in 24.3.0-asahi20241104 (will be pushed to the repos soon). |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
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: |
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 |
@asahilina I think following two bugs in your list above can be marked as resolved(?):
|
This is a tracker bug for general GPU issues, like:
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, tryLIBGL_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 withnocompress
so we can take a look and determine whether it's an app bug or a driver bug!Known issues
Resolved issues
Issues that aren't driver bugs
Google Sheets bugFirefox bug) (workaround:ASAHI_MESA_DEBUG=no16
)The text was updated successfully, but these errors were encountered: