QObject::killTimer Warning Messages

[wysota]

What\Who is deleting the QTimer?

Provided that the timer doesn't have a parent it has to be you or the timer is not deleted at all.

Why is the m_pTimer value valid immediately after exec() returns but invalid when isActive() is called?

Maybe you have a local variable somewhere that is named the same and it shadows the other variable?

Would it be better to handle the deletion of m_pTimer in response to the QThread::finished() signal?

No. If you create an object in run(), destroy it there. The timer won't timeout anyway after you return from exec() so there is no point in keeping it. I even suggest you change your run() a bit:

void ...:run(){
  QTimer timer;
  connect(&timer, SIGNAL(timeout()), this, SLOT(checkTimestamp()));
  timer.start(5000);
  exec();
  // the timer will get deleted when run() returns
}

void ...:run(){
  QTimer timer;
  connect(&timer, SIGNAL(timeout()), this, SLOT(checkTimestamp()));
  timer.start(5000);
  exec();
  // the timer will get deleted when run() returns
}

To copy to clipboard, switch view to plain text mode 

By the way, I hope you realize the slot will be called in the context of the main thread and not the worker thread. What is the point in doing all that in a worker thread anyway? Does the thread do anything else besides running the timer?

[mclark]

Provided that the timer doesn't have a parent it has to be you or the timer is not deleted at all.

Even when I remove the 'delete m_pTimer' code the m_pTimer value changes after returning from exec(). It gets the 0xfeeefeee value. There are no other m_pTimer variables declared anywhere in this class.

By the way, I hope you realize the slot will be called in the context of the main thread and not the worker thread. What is the point in doing all that in a worker thread anyway? Does the thread do anything else besides running the timer?

The purpose of this thread is to:

1. Maintain a list of objects. When the object is created it is put into the list. When the object is fully initialized (due to outside forces) it is removed from the list.
2. Run the timer. When the timer times out, the list is checked. If it contains any objects that have been waiting to be initialized for too long, they are rescheduled and removed from the list. At this point the timer is restarted.

I admit I am a novice when it comes to threading, but I don't see why the slot is run in the main threads context instead of the worker thread. The 'this' pointer in the connect() call is the worker thread pointer, no?

[wysota]

The purpose of this thread is to:

1. Maintain a list of objects. When the object is created it is put into the list. When the object is fully initialized (due to outside forces) it is removed from the list.
2. Run the timer. When the timer times out, the list is checked. If it contains any objects that have been waiting to be initialized for too long, they are rescheduled and removed from the list. At this point the timer is restarted.

You don't need a separate thread for that.

I admit I am a novice when it comes to threading, but I don't see why the slot is run in the main threads context instead of the worker thread. The 'this' pointer in the connect() call is the worker thread pointer, no?

No, it is a pointer to an object representing the thread. And the object itself lives in the context of the thread that created it (the object, not the thread) therefore it lives in context of the main thread.