-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Raspberry Pi 5 Surface::configure panic #2552
Comments
I've got the same issue if I call maximize on impl Application::new: Anti-aliasing is set to false. Screen size is: 2560x1600 (or 1600x2560 doesn't matter) Also on rpi5 bookworm 64bit wayland defaults, and it's a showstopper for me. |
+1, also experiencing this on Raspberry Pi 5 running Raspberry Pi OS when using wgpu renderer (but not with tiny-skia renderer). Fullscreen doesn't matter, if I resize the app's height or width above 2048 pixels it immediately crashes. |
Is your issue REALLY a bug?
Is there an existing issue for this?
Is this issue related to iced?
What happened?
I'm working on a project that runs on a Raspberry Pi 5 in a kiosk mode using Cage (Wayland compositor with a single fullscreen app). This works fine on a small touchscreen display, V3D is detected and working. But if I try use external display with 3840x2160 resolution, it panics with this error:
What is the expected behavior?
Raspberry Pi 5 should be able to handle that resolution without issues. After looking into
vulkaninfo
output, it seems to me that this is an issue of default wgpu surface limits requesting too much, while down level limits - too little. I've attached limits of V3D as log output, would appreciate it if anyone comes up with a good way to fix this.Seems like currently the list of possible limits is hardcoded, and I don't think that exposing this as an additional setting is a good approach. Maybe this list could include Raspberry Pi specific case? If not - I guess this is not an issue report after all, but just another feature request pretending to be one. Specifically to get more control over wgpu configuration.
Version
crates.io release
Operating System
Linux
Do you have any log output?
The text was updated successfully, but these errors were encountered: