sleep or delay in qthread but crash

[QtTester]

@SGaist the pointer has been inited. and it is not crash at the begining. it crash at an unexpected time.

      // this version will still crash, even no pointer.
       QEventLoop el;
        QTimer::singleShot(msec,&el,&QEventLoop::quit);
        el.exec(QEventLoop::ExcludeUserInputEvents);

@JonB i am using debugger,but cannot analyse how it is going on.
unless i need to debug the qt source file?

[Pl45m4]

@QtTester said in sleep or delay in qthread but crash:

  // this version will still crash, even no pointer.
   QEventLoop el;
    QTimer::singleShot(msec,&el,&QEventLoop::quit);
    el.exec(QEventLoop::ExcludeUserInputEvents);

What's the point of all this?
You probably don't need it when using a worker thread.

Simplify your app / worker / thread class until it doesn't crash anymore

[QtTester]

@Pl45m4 need to query some io status:

//call it like this:
dosomething();
while(1){
    if(io() ==0)
      break;
    delay(1);
}
dootherthing();

[Christian Ehrlicher]

@QtTester said in sleep or delay in qthread but crash:

need to query some io status:

Then use a QTimer with the Worker-Object approach shown in the documentation: https://doc.qt.io/qt-6/qthread.html#details

[QtTester]

@Christian-Ehrlicher we may not write code like that. it is a long long complicate procedure, and will delay for many condition with many times.

[JonB]

@QtTester
I already wrote above https://forum.qt.io/post/816186 that you should abandon all this event loop and waiting stuff. It's not complicated, it doesn't introduce extra delays and can be used many times.

Otherwise do your best to debug your code. You have already said you have made a change per @SGaist and that has changed where the crash is, so who knows what is going on.

[Christian Ehrlicher]

@QtTester so either try to fix this crappy code or rewrite it - I would say the latter costs less, especially in the long run.

[QtTester]

i trace the qt source file,it stop right here, is qstring .append() possible has a bug???,version is 5.14.1:

more:

[jsulm]

@QtTester Before assuming a bug in Qt you should make sure it is not your code doing something wrong. The fact that the crash is in Qt code does not mean the issue is in Qt. Since you're writing quite convoluted code in this case I'm quite sure the issue is on your side.

[Christian Ehrlicher]

This looks like two other threads in the last few days - don't mix debug and release libraries.

[SimonSchroeder]

Usually, it is your own code and not Qt's (I've been using Qt for 20 years and this is still true for me). Go down the stacktrace until you find your own code. See how you call Qt and most likely there is some wrong value there. Also, since you are using more than one thread, look in the stacktraces of all threads that have your own code running.

[JonB]

@Christian-Ehrlicher For the record, we seem to have a fair number of debug/release library mixing recently.

[QtTester]

I set qdebug level to qwarning, the crash disappeared! strange

[SimonSchroeder]

@QtTester said in sleep or delay in qthread but crash:

I set qdebug level to qwarning, the crash disappeared! strange

This is not strange at all. You have just disabled any line with qDebug() in your source. As I have said before your error is most likely in your own code. Now, that the erroneous memory address is not accessed by qDebug() anymore the bug vanishes. You can also just remove the offending qDebug() line in your source (right where it crashed in your stacktrace) and everything works fine as well. Then, you can continue to use qDebug() everywhere else.