diff options
| author | Cristian Maureira-Fredes <Cristian.Maureira-Fredes@qt.io> | 2020-04-28 16:50:25 +0200 |
|---|---|---|
| committer | Cristian Maureira-Fredes <Cristian.Maureira-Fredes@qt.io> | 2020-04-30 07:20:55 +0200 |
| commit | 270d2be98ad72e0cffb20339c3a42c8f81e3b8ec (patch) | |
| tree | ad48835cfe46f504376d09be4a4d14d84eab4636 /sources/pyside2/tests/QtWebKit/shouldInterruptjavascript_test.py | |
| parent | a30d24ebfea35ff883a67524fe8b1221ed1dc73d (diff) | |
QMutexLocker allow-thread in constructor
After the improvement to the GIL treatment inside PySide
to avoid UI freezing issues, many functions need an entry
on the typesystem to allow thread explicitly, this was
the case of the report, where a QMutexLocker was initialized.
The initialization was done inside a QThread run method,
so the lack of allow-thread was generating a deadlock.
The nogil section of the code (from Cython)
was not related to the issue, since replacing the content with
any instruction produced the deadlock anyways.
Fixes: PYSIDE-1271
Change-Id: Ib1fd1ebd923c3f9dc9ae390228bcf40b5b878019
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Diffstat (limited to 'sources/pyside2/tests/QtWebKit/shouldInterruptjavascript_test.py')
0 files changed, 0 insertions, 0 deletions