Yeah the weirdest part for me was that it carried to a new install; I’ve NEVER seen another program where that happened. But it happened THREE different times, it 100% carried over, or at the least was so inherent to something in my setup that it started happening again within 2 days of re-installing.
Yeah the weirdest part for me was that it carried to a new install; I’ve NEVER seen another program where that happened. But it happened THREE different times, it 100% carried over, or at the least was so inherent to something in my setup that it started happening again within 2 days of re-installing.
Try disabling HTTP/3 (
network.http.http3.enable).