Bug 795 – QThread blocks GUI thread on Windows 7

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 795 - QThread blocks GUI thread on Windows 7

Summary:

QThread blocks GUI thread on Windows 7

Status:	CLOSED INVALID

Product:	PySide
Classification:	Unclassified
Component:	PySide
Version:	1.0.0
Platform:	PC MS Windows XP/Vista/7

Importance:	P5 major
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-03-29 04:58 EEST by cymrow
Modified:	2011-04-01 23:16 EEST (History)
CC List:	8 users (show)

See Also:

Attachments
testcase (1.28 KB, text/plain) 2011-03-29 04:59 EEST, cymrow	Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description cymrow 2011-03-29 04:58:04 EEST

When a QThread running an eventloop receives a signal that was connected with
Qt.QueuedConnection, the emitting thread blocks. See the attachment for code
that demonstrates this behavior. The same script behaves normally on OS X.

A possibly related issue is that connecting a signal in a different thread does
not seem to automatically use Qt.QueuedConnection, as the documentation
suggests. For example, removing the second argument on line 10 of the
attachment should automatically create a QueuedConnection since it is connected
in a different thread than the thread that eventually emits the signal.

Comment 1 cymrow 2011-03-29 04:59:50 EEST

Created attachment 294 [details]
testcase

Comment 2 cymrow 2011-03-29 07:09:12 EEST

PyQt4 is doing the same thing. I must be doing something wrong.

Comment 3 Hugo Parente Lima 2011-04-01 23:16:05 EEST

Closing bug after release of PySide 1.0.1.