Warnings spammed in Log

[richardewert]

When I resize the game window these warnings are spammed in the log:

WARN log: Requested size 1018x757 is outside of the supported range: Extent3d { width: 990, height: 757, depth_or_array_layers: 1 }..=Extent3d { width: 990, height: 757, depth_or_array_layers: 1 }
WARN log: Requested size 990x757 is outside of the supported range: Extent3d { width: 991, height: 757, depth_or_array_layers: 1 }..=Extent3d { width: 991, height: 757, depth_or_array_layers: 1 }
WARN log: Requested size 991x757 is outside of the supported range: Extent3d { width: 1001, height: 757, depth_or_array_layers: 1 }..=Extent3d { width: 1001, height: 757, depth_or_array_layers: 1 }
WARN log: Requested size 1001x757 is outside of the supported range: Extent3d { width: 1002, height: 757, depth_or_array_layers: 1 }..=Extent3d { width: 1002, height: 757, depth_or_array_layers: 1 }
WARN log: Requested size 1002x757 is outside of the supported range: Extent3d { width: 1089, height: 757, depth_or_array_layers: 1 }..=Extent3d { width: 1089, height: 757, depth_or_array_layers: 1 }
WARN log: Requested size 1089x757 is outside of the supported range: Extent3d { width: 1091, height: 757, depth_or_array_layers: 1 }..=Extent3d { width: 1091, height: 757, depth_or_array_layers: 1 }

It looks very similar to #1003 but that should've been fixed ages ago.
There is also another warning right after starting the application:

WARN log: EGL says it can present to the window but not natively

System info:

INFO bevy_render::renderer: AdapterInfo { name: "NVIDIA GeForce GTX 1070", driver: "NVIDIA", driver_info: "545.29.06", backend: Vulkan }
INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Linux 22.04 Pop!_OS", kernel: "6.6.6-76060606-generic", cpu: "AMD Ryzen 9 3900X 12-Core Processor", core_count: "12", memory: "15.5 GiB" }

Is this a common Problem and can I do something about it? I couldn't find anything on this.

[TimJentzsch]

Do you get this for every game or only when you are using a specific setup?
Maybe you can try running a couple of Bevy examples and see if the same thing happens.
I'm also on Pop!_OS and didn't encounter this yet.

If your game is open source or if you're able to provide a minimal reproducible example, that would help a lot! :)

[richardewert]

Thanks for the help!
I ran the some examples (window_resizing, window_settings) and had the same warnings and additionally also a new error message that are both spammed when resizing the window:

WARN log: Requested size 1246x757 is outside of the supported range: Extent3d { width: 1237, height: 757, depth_or_array_layers: 1 }..=Extent3d { width: 1237, height: 757, depth_or_array_layers: 1 }
ERROR log: VALIDATION [VUID-VkSwapchainCreateInfoKHR-pNext-07781 (0x4c8929c1)]
        Validation Error: [ VUID-VkSwapchainCreateInfoKHR-pNext-07781 ] | MessageID = 0x4c8929c1 | vkCreateSwapchainKHR(): pCreateInfo->imageExtent (1246, 757), which is outside the bounds returned by vkGetPhysicalDeviceSurfaceCapabilitiesKHR(): currentExtent = (1237,757), minImageExtent = (1237,757), maxImageExtent = (1237,757). The Vulkan spec states: If a VkSwapchainPresentScalingCreateInfoEXT structure was not included in the pNext chain, or it is included and VkSwapchainPresentScalingCreateInfoEXT::scalingBehavior is zero then imageExtent must be between minImageExtent and maxImageExtent, inclusive, where minImageExtent and maxImageExtent are members of the VkSurfaceCapabilitiesKHR structure returned by vkGetPhysicalDeviceSurfaceCapabilitiesKHR for the surface (https://vulkan.lunarg.com/doc/view/1.3.268.0/linux/1.3-extensions/vkspec.html#VUID-VkSwapchainCreateInfoKHR-pNext-07781)

But the example features work as intended.
This new error message now also shows up when running my original bevy project.
I can reproduce it with this code (I'm using Bevy 0.12.1):

use bevy::prelude::*;
use bevy::window::{PresentMode, Window, WindowPlugin, WindowTheme};
use bevy::log::{Level, LogPlugin};
use bevy::diagnostic::{FrameTimeDiagnosticsPlugin, LogDiagnosticsPlugin};
fn main() {
    App::new()
        .add_plugins((
            DefaultPlugins
                .set(WindowPlugin {
                    primary_window: Some(Window {
                        title: "Reproduce warnings and errors when resizing".into(),
                        resolution: (1280., 720.).into(),
                        present_mode: PresentMode::AutoVsync,
                        fit_canvas_to_parent: true,
                        prevent_default_event_handling: true,
                        window_theme: Some(WindowTheme::Dark),
                        resizable: true,
                        ..Default::default()
                    }),
                    ..Default::default()
                })
                .set(LogPlugin {
                    filter: "info,wgpu=warn,wgpu_hal=warn,mygame=debug".into(),
                    level: Level::DEBUG,
                }),
            FrameTimeDiagnosticsPlugin::default(),
            LogDiagnosticsPlugin::default(),
        ))
        .run();
}

Since the examples also had this error I assume this is a "my setup problem".

[TimJentzsch]

Interesting, with this code I get similar problems.

For me it spams the following on resize:

WARN present_frames: log: Suboptimal present of frame 2 

Then occasionally I get:

WARN log: Requested size 1371x434 is outside of the supported range: Extent3d { width: 1367, height: 437, depth_or_array_layers: 1 }..=Extent3d { width: 1367, height: 437, depth_or_array_layers: 1 }    

And just once:

WARN log: InstanceFlags::VALIDATION requested, but unable to find layer: VK_LAYER_KHRONOS_validation  
WARN log: Detected skylake derivative running on mesa i915. Clears to srgb textures will use manual shader clears.  

System info:

AdapterInfo { name: "Intel(R) Graphics (ADL GT2)", vendor: 32902, device: 17958, device_type: IntegratedGpu, driver: "Intel open-source Mesa driver", driver_info: "Mesa 23.3.0-1pop0~1702935939~22.04~67e417a", backend: Vulkan }
SystemInfo { os: "Linux 22.04 Pop!_OS", kernel: "6.6.6-76060606-generic", cpu: "12th Gen Intel(R) Core(TM) i7-1260P", core_count: "12", memory: "15.3 GiB" }

[TeamDman]

maybe this always happens and the log plugin is what brings it out?

I have a similar problem where the window being minimized spams the logs

add_plugins(DefaultPlugins.set(LogPlugin {
        level: bevy::log::Level::DEBUG,
        filter: "info".into(),
    }).build())