rnhmjoj/qutebrowser
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Don't call processEvents in NetworkManager.

Browse Source 
This caused the segfaults and memory corruption issues mentioned in #256.
This commit is contained in:
Florian Bruhin 2014-11-18 07:08:06 +01:00
parent 3622f35865
commit 2514e66028
1 changed files with 0 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
qutebrowser/network/networkmanager.py
View File

@ -46,11 +46,6 @@ class NetworkManager(QNetworkAccessManager):
""" """
def __init__(self, win_id, parent=None): 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") log.init.debug("Initializing NetworkManager")
with log.disable_qt_msghandler(): with log.disable_qt_msghandler():
# WORKAROUND for a hang when a message is printed - See: # WORKAROUND for a hang when a message is printed - See: