| Ticket UUID: | 0dda4935234bff36810e88d44103812d753df845 | |||
| Title: | Qt network operation stalls Ripcord for long time periods | |||
| Status: | Closed | Type: | Bug | |
| Severity: | Minor | Priority: | Low | |
| Subsystem: | Windows | Resolution: | Unable_To_Reproduce | |
| Last Modified: | 2019-08-10 22:10:14 | |||
| Version Found In: | 0.3.3 | |||
nakst — 2018-09-22 17:32:37Windows 7. A bug in Qt causes an apparently-asynchronous network operation to stall the UI until a timeout (~1 minute) is reached. This causes the whole program to lock up, displaying the "Program not responding" message. It only occurs sometimes when activating the window. | ||||
tmad40blue — 2018-09-22 17:38:20Do you have a link to the Qt bug? | ||||
tmad40blue — 2018-09-22 17:53:31Updated title to be more accurate. | ||||
cancel — 2018-09-23 08:05:25Affects one known user (nakst) on Windows 7. Probably related to QNetworkAccessManager trying to look up HTTP proxy information. | ||||
|
cancel — 2019-08-10 22:10:00 It turns out the user had VirtualBox installed. VirtualBox is dangerously low-quality software with many bugs, and it inserts itself into the kernel via drivers and causes problems on every OS (Windows, Mac, Linux.) In this case, its virtual network drivers were malfunctioning and causing random programs in userspace to lock up. It's a violation of galactic federal regulations to report bugs in any software if you have VirtualBox installed on your system. Unfortunately, the user violated this prime directive, and the result is wasted hours of debugging time. | ||||