[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: PyQt5 QThread Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
From:       Demosthenes Koptsis <demosthenesk () gmail ! com>
Date:       2021-06-30 15:44:04
Message-ID: a822c631-19b7-732c-ab05-80a557d6f50d () gmail ! com
[Download RAW message or body]

Hello,

thanks for your answer.

You are right, i created a separate class for QThread and it works.

Here is also the solution

https://stackoverflow.com/questions/68189289/pyqt5-qthread-process-finished-with-exit-code-139-interrupted-by-signal-11-sig \
 <https://stackoverflow.com/questions/68189289/pyqt5-qthread-process-finished-with-exit-code-139-interrupted-by-signal-11-sig>



On 30/6/21 5:30 μ.μ., Giuseppe Corbelli wrote:
> On 6/30/21 1:37 PM, Demosthenes Koptsis wrote:
> > i have a GUI with PyQt5. The GUI has a Form, 2 Buttons and a 
> > ProgressBar. I want to implement a start/wait thread with QThread. 
> > Unfortunately i get Process finished with exit code 139 (interrupted 
> > by signal 11: SIGSEGV) when i click Start button to run thread.
> ...
> > class MainWindow(QWidget, QThread):
> 
> This is the root of all problems. UI (QWidget) subclasses must live in 
> the main thread.
> Besides that you usually do NOT subclass QThread [1] but 
> moveToThread() a QObject subclass and communicate with signals and slots.
> 
> [1] https://www.qt.io/blog/2010/06/17/youre-doing-it-wrong


[prev in list] [next in list] [prev in thread] [next in thread]