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

panicked at 'No surface found for window.' #3248

Open
LCW-QAQ opened this issue Dec 4, 2021 · 1 comment
Open

panicked at 'No surface found for window.' #3248

LCW-QAQ opened this issue Dec 4, 2021 · 1 comment
Labels
A-Windowing Platform-agnostic interface layer to run your app in C-Bug An unexpected or incorrect behavior P-Regression Functionality that used to work but no longer does. Add a test for this!

Comments

@LCW-QAQ
Copy link

LCW-QAQ commented Dec 4, 2021

Bevy version

git head 4423a2f

Operating system & version

Windows 10

What you did

When minimizing windows, panicked at 'No surface found for window.'

What you expected to happen

The window is minimized and there is no panic

What actually happened

The actual result of the actions you described.

Additional information

// main.rs
use bevy::prelude::*;

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .run();
}
# Cargo.toml
[package]
name = "bevy_examples"
version = "0.1.0"
edition = "2021"

[dependencies]
bevy = { git = "https://gitee.com/lcw_qaq/bevy", features = ["dynamic"] }

panic info

thread 'main' panicked at 'No surface found for window.', C:\Users\LCW\.cargo\git\checkouts\bevy-09c88e8028296690\4423a2f\crates\bevy_wgpu\src\renderer\wgpu_render_resource_context.rs:372:14

// panic function
fn configure_surface(&self, window: &Window) {
        let surfaces = self.resources.window_surfaces.read();

        let surface_configuration: wgpu::SurfaceConfiguration = window.wgpu_into();
        let surface = surfaces
            .get(&window.id())
            .expect("No surface found for window.");
        surface.configure(&self.device, &surface_configuration);
    }
@LCW-QAQ LCW-QAQ added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled labels Dec 4, 2021
@alice-i-cecile alice-i-cecile added A-Windowing Platform-agnostic interface layer to run your app in P-Regression Functionality that used to work but no longer does. Add a test for this! and removed S-Needs-Triage This issue needs to be labelled labels Dec 4, 2021
@alice-i-cecile
Copy link
Member

Regression of #2299 (previous central issue). #2300 is merged, and should have fixed the existing issue.

This however looks like a new bug we introduced, given that the error is different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Windowing Platform-agnostic interface layer to run your app in C-Bug An unexpected or incorrect behavior P-Regression Functionality that used to work but no longer does. Add a test for this!
Projects
None yet
Development

No branches or pull requests

2 participants