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.

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

DCP has crashed #359

Open
odlg opened this issue Jan 6, 2025 · 3 comments
Open

DCP has crashed #359

odlg opened this issue Jan 6, 2025 · 3 comments

Comments

@odlg
Copy link

odlg commented Jan 6, 2025

I am on Fedora 41 and seeing "DCP has crashed" errors when using a 4K display attached via HDMI on my MacBook Pro M2 Pro. It happens with kernel 6.12.4-400.asahi.fc41.aarch64+16k - I have not seen it with earlier kernels. It is easily reproduceable.
When using 6.12.1-404.asahi.fc41.aarch64+16k I do not see the issue.

I can make DCP crash, frequently within minutes, using Freeshow (an Electron application), forcing it to use wayland (--ozone-platform=wayland) and having full-screen video on the external display.
dmesg.dcp-has-crashed.log

@shaunduncan
Copy link

I am seeing this same issue, also running 6.12.4-400.asahi.fc41.aarch64+16k on M2 MackBook Pro. It happens while I have an external display connected via HDMI. I have not found a way to reliably reproduce the issue, but when it happens, the external day acts like it has disconnected, but still shows whatever was last displayed. The display configuration menu doesn't show the display but it acts like it's there:

Screenshot_20250107_105405

@odlg
Copy link
Author

odlg commented Jan 8, 2025

I just had another crash. This time it was the HDMI connected monitor that survived and the internal MacBook M2 Pro screen that is "disconnected". The entire desktop was frozen for 15 seconds or so.
dmesg.dcp-has-crashed2.log

@steffenvongrabau
Copy link

Your error log clearly shows the following error message:
[ 45.864390] apple-drm soc:display-subsystem: Plane operation would have crashed DCP! Rejected!
DCP requires 32x32 of every plane to be within screen space. Your compositor asked to overlay [3449x95, 3456x143] on 3456x2160. This is not supported, and your compositor should have switched to software compositing when this operation failed. You should not have noticed this at all. If your screen froze/hitched, or your compositor crashed, please report this to the your compositor's developers. We will not throw this error again until you next reboot.

This issue is caused by your compositor. Please report this at their repository and close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants