https://bugs.kde.org/show_bug.cgi?id=352055

--- Comment #38 from David Edmundson <k...@davidedmundson.co.uk> ---
At first these look identical, but on closer inspection of QTimer:

void     singleShot(int msec, Qt::TimerType timerType, const QObject *
receiver, const char * member)
void     singleShot(int msec, const QObject * receiver, PointerToMemberFunction
method)

behave differently when msec == 0
the first version has a shortcut path that does a QMetaObject::invokeMethod
with QtQueuedConnection.

The latter does not and goes via an actual timer; which possibly means it's
called directly? 

Definitely not the true "cause" of the bug, but I'm willing to believe this has
a significant impact on whether we hit the bug or not.

+1 to merging this.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to