Yehowshua/ZIm
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Use trace log level for potentially high-volume vsync duration log (#36147)

Browse source 
This is an attempt to fix
https://github.com/zed-industries/zed/issues/36125

Release Notes:

- N/A
This commit is contained in:
Max Brunsfeld 2025-08-13 14:45:34 -07:00 • committed by GitHub
parent 8452532c8f
commit 09e90fb023
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
crates/gpui/src/platform/windows/vsync.rs
View file

@ -99,7 +99,7 @@ impl VSyncProvider {
// operation for the first call after the vsync thread becomes non-idle, // operation for the first call after the vsync thread becomes non-idle,
// but it shouldn't happen often. // but it shouldn't happen often.
if !wait_succeeded || elapsed < VSYNC_INTERVAL_THRESHOLD { if !wait_succeeded || elapsed < VSYNC_INTERVAL_THRESHOLD {
log::warn!("VSyncProvider::wait_for_vsync() took shorter than expected"); log::trace!("VSyncProvider::wait_for_vsync() took less time than expected");
std::thread::sleep(self.interval); std::thread::sleep(self.interval);
} }
} }