From 2514e66028b85d270cfb6d4707e52c00bcec8c1d Mon Sep 17 00:00:00 2001 From: Florian Bruhin Date: Tue, 18 Nov 2014 07:08:06 +0100 Subject: [PATCH] Don't call processEvents in NetworkManager. This caused the segfaults and memory corruption issues mentioned in #256. --- qutebrowser/network/networkmanager.py | 5 ----- 1 file changed, 5 deletions(-) diff --git a/qutebrowser/network/networkmanager.py b/qutebrowser/network/networkmanager.py index b395a82a7..a56c30003 100644 --- a/qutebrowser/network/networkmanager.py +++ b/qutebrowser/network/networkmanager.py @@ -46,11 +46,6 @@ class NetworkManager(QNetworkAccessManager): """ def __init__(self, win_id, parent=None): - # It seems QNetworkAccessManager somehow calls processEvents which - # causes some trouble, so we try to process outstanding events here - # first. - app = objreg.get('app') - app.processEvents() log.init.debug("Initializing NetworkManager") with log.disable_qt_msghandler(): # WORKAROUND for a hang when a message is printed - See: