glzr-io
[Bug] Severe packet loss running GlazeWM
Describe the bug
I'm experiencing severe packet loss when running GlazeWM on Windows 11 Enterprise (Version 10.0.22621 Build 22621). The issue was first noticed when performance degraded during Google Meet calls, but I've since confirmed it's consistently reproducible using Cloudflare's speedtest.
I appreciate this could be a software/hardware interaction however other tiling window managers do not exhibit the same behaviour.
Reproduction Steps
Install GlazeWM on Windows 11 Enterprise (Version 10.0.22621 Build 22621) Launch GlazeWM Run Cloudflare speedtest (https://speed.cloudflare.com/) Observe significant packet loss Close GlazeWM Run speedtest again and observe normal network performance
Expected Behavior Network performance should remain stable regardless of whether GlazeWM is running.
Actual Behavior When GlazeWM is active, severe packet loss occurs consistently (100% reproducible on this device). This affects all network applications, with Google Meet being where I first noticed degraded performance. The issue resolves immediately when GlazeWM is closed.
Environment OS: Microsoft Windows 11 Enterprise OS Version: 10.0.22621 Build 22621 Application: GlazeWM (latest version) Network testing tool: Cloudflare speedtest
Additional Information
The issue appears to be specific to GlazeWM, as other applications run normally when GlazeWM is not active The packet loss is immediate when GlazeWM launches and resolves as soon as it's closed No relevant errors appear in Windows Event Viewer Network adapter and drivers are up to date
Version number
3.8.1
Are you also running Zebar? There was a similar issue with specific VPN's that someone brought up here: #159. Could it be the same issue?
@lars-berger yes, apologies I have logged this against the wrong applications - it is actually zebar, without zebar running there is no packet loss.
I am not connected via a VPN and removing the network provider from Zebar also corrects the issue.
@lars-berger What do you think about tackling this issue, by replacing IP based IPC, with native to windows named pipes?
I am interested in this, mostly because of #628 and doing this, might also fix the internet instability issues.
