bevyengine / bevyengine/bevy

monitor_info takes an extremely long time creating windows

Open
#17,640 6 comments 0 reactions 0 assignees View on GitHub
A-Windowing C-Bug O-Linux S-Needs-Testing
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 16h
Merged PRs (30d)
171

Description

## Bevy version

0.15.1

## \[Optional\] Relevant system information

Rust 1.84.1
Arch Linux
AMD Radeon RX 7800 XT (RADV NAVI32)
KDE Plasma (Wayland)

## What you did

Run `cargo run --example monitor_info` on the 0.15.1 tag of bevy.

## What went wrong

The windows for each monitor are only created after several minutes of waiting:

```
2025-02-02T02:03:21.079119Z TRACE wgpu_core::device::global: Device::create_compute_pipeline -> Id(3,1)
2025-02-02T02:06:57.382343Z TRACE Poller::wait{timeout=None}:wait{epoll_fd=6 timeout=None}: polling::epoll: new events epoll_fd=6 res=1
2025-02-02T02:06:57.382565Z TRACE calloop::loop_logic: [calloop] Dispatching events for source #0
```

After waiting, both windows (one for each monitor I have) spawn at the same time.

## Additional information

Other examples create windows fine. Window mode nor transparency seems to matter.

Log with `RUST_LOG=trace` from `monitor_info`: [monitor_info.txt](https://github.com/user-attachments/files/18630922/monitor_info.txt)

`--features wayland` does not seem to affect it.

Contributor guide

Open the contributing guide

Research direction

Start by running `cargo run --example monitor_info` on the 0.15.1 tag with the reported Wayland setup and inspect the linked `monitor_info.txt` trace around window creation, device creation, and event polling. Done means the example creates its monitor windows without the multi-minute delay while other examples remain unaffected.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.