QHostInfo::lookupHost - a slot gets executed in a wrong thread

Unlike legacy overloads, working with SLOT macro, the new version, accepting a pointer to member-function calls this member-function on a wrong thread (not the thread that initiates a lookup). Such a behavior, if intended, must be properly documented not to surprise its users.

With the example attached I have this:

ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to objects owned by a different thread. Current thread 0x0x7fb991fa3e80. Receiver 'lookupButton' (of type 'QPushButton') was created in thread 0x0x7fb991d075e0", file kernel/qcoreapplication.cpp, line 576
Abort trap: 6