How make QIODevice::writeData work asynchronously?

SGaist

Hi,

The QObject::moveToThread function might be what you need.

fpartl

Thank you for reply. I dont know if I should move to thred whole class with QAudioInput a QIODevice objects or just QIODevice. I will try something.

SGaist

Usually you move the whole object, don't forget to parent things correctly to have everything moved properly.

fpartl

I have done the work. I have created the the AudioWorker class witch inherits QObject. Then I maked QAudioInput and QIODevice in here and I make a forward of signals from QIODevice to catch calculated data. I moved AudioWorker to QThread and pressed the Run button. But program crash on segmentation fault in QIODevice even if I comment the whole code in writeData method.

SGaist

Without the code and the backtrace, it's pretty much Crystal Ball Debugging so here goes: did you check that you have everything initialised properly before using ?

fpartl

Ou, I am sorry. The code is on GitHub. I wrote the AudioWorker class and program fails after I close the MainWindow with

The program has unexpectedly finished.
C:\Users\frant\QtProjects\build-PocketEar-Desktop_Qt_5_8_0_MinGW_32bit-Debug\debug\PocketEar.exe crashed.

In the AudioWorker there is instances of QAudioInput and QIODevice(MFCCPerformer).
In the debug mode I got segmentation fault after MainWindow close on line 28 in AudioWorker (audioInput->suspend()). I think I am wrong with a closing of the thread. Thank for help.

SGaist

Do you have a complete stack trace ?

Note that you are doing a double delete with audioInput and mfcc. Both of them have a parent so they will be delete when AudioWorker gets deleted.

fpartl

Here is a stack trace after failure. I really appreciate your help. I am new in this problematics.

Stack trace

fpartl

I figured it out! serverStateChanged call pause method on alredy destroyed object. Now it works. What a thing! Thank you for help! :-)

SGaist

You're welcome !

Since you have found the error, please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found :)