/usr/share/qt5/doc/qtdoc/threads-qobject.html is in qt5-doc-html 5.9.5-0ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 | <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- threads.qdoc -->
<title>Threads and QObjects | Qt 5.9</title>
<link rel="stylesheet" type="text/css" href="style/offline-simple.css" />
<script type="text/javascript">
document.getElementsByTagName("link").item(0).setAttribute("href", "style/offline.css");
// loading style sheet breaks anchors that were jumped to before
// so force jumping to anchor again
setTimeout(function() {
var anchor = location.hash;
// need to jump to different anchor first (e.g. none)
location.hash = "#";
setTimeout(function() {
location.hash = anchor;
}, 0);
}, 0);
</script>
</head>
<body>
<div class="header" id="qtdocheader">
<div class="main">
<div class="main-rounded">
<div class="navigationbar">
<table><tr>
<td ><a href="index.html">Qt 5.9</a></td><td >Threads and QObjects</td></tr></table><table class="buildversion"><tr>
<td id="buildversion" width="100%" align="right">Qt 5.9.5 Reference Documentation</td>
</tr></table>
</div>
</div>
<div class="content">
<div class="line">
<div class="content mainContent">
<link rel="prev" href="threads-reentrancy.html" />
<link rel="next" href="threads-modules.html" />
<p class="naviNextPrevious headerNavi">
<a class="prevPage" href="threads-reentrancy.html">Reentrancy and Thread-Safety</a>
<span class="naviSeparator"> ◦ </span>
<a class="nextPage" href="threads-modules.html">Thread-Support in Qt Modules</a>
</p><p/>
<div class="sidebar">
<div class="toc">
<h3><a name="toc">Contents</a></h3>
<ul>
<li class="level1"><a href="#qobject-reentrancy">QObject Reentrancy</a></li>
<li class="level1"><a href="#per-thread-event-loop">Per-Thread Event Loop</a></li>
<li class="level1"><a href="#accessing-qobject-subclasses-from-other-threads">Accessing QObject Subclasses from Other Threads</a></li>
<li class="level1"><a href="#signals-and-slots-across-threads">Signals and Slots Across Threads</a></li>
</ul>
</div>
<div class="sidebar-content" id="sidebar-content"></div></div>
<h1 class="title">Threads and QObjects</h1>
<span class="subtitle"></span>
<!-- $$$threads-qobject.html-description -->
<div class="descr"> <a name="details"></a>
<p><a href="../qtcore/qthread.html">QThread</a> inherits <a href="../qtcore/qobject.html">QObject</a>. It emits signals to indicate that the thread started or finished executing, and provides a few slots as well.</p>
<p>More interesting is that <a href="../qtcore/qobject.html">QObject</a>s can be used in multiple threads, emit signals that invoke slots in other threads, and post events to objects that "live" in other threads. This is possible because each thread is allowed to have its own event loop.</p>
<a name="qobject-reentrancy"></a>
<h2 id="qobject-reentrancy">QObject Reentrancy</h2>
<p><a href="../qtcore/qobject.html">QObject</a> is reentrant. Most of its non-GUI subclasses, such as <a href="../qtcore/qtimer.html">QTimer</a>, <a href="../qtnetwork/qtcpsocket.html">QTcpSocket</a>, <a href="../qtnetwork/qudpsocket.html">QUdpSocket</a> and <a href="../qtcore/qprocess.html">QProcess</a>, are also reentrant, making it possible to use these classes from multiple threads simultaneously. Note that these classes are designed to be created and used from within a single thread; creating an object in one thread and calling its functions from another thread is not guaranteed to work. There are three constraints to be aware of:</p>
<ul>
<li><i>The child of a <a href="../qtcore/qobject.html">QObject</a> must always be created in the thread where the parent was created.</i> This implies, among other things, that you should never pass the <a href="../qtcore/qthread.html">QThread</a> object (<code>this</code>) as the parent of an object created in the thread (since the <a href="../qtcore/qthread.html">QThread</a> object itself was created in another thread).</li>
<li><i>Event driven objects may only be used in a single thread.</i> Specifically, this applies to the <a href="../qtcore/timers.html">timer mechanism</a> and the <a href="../qtnetwork/qtnetwork-module.html">network module</a>. For example, you cannot start a timer or connect a socket in a thread that is not the <a href="../qtcore/qobject.html#thread">object's thread</a>.</li>
<li><i>You must ensure that all objects created in a thread are deleted before you delete the <a href="../qtcore/qthread.html">QThread</a>.</i> This can be done easily by creating the objects on the stack in your <a href="../qtcore/qthread.html#run">run()</a> implementation.</li>
</ul>
<p>Although <a href="../qtcore/qobject.html">QObject</a> is reentrant, the GUI classes, notably <a href="../qtwidgets/qwidget.html">QWidget</a> and all its subclasses, are not reentrant. They can only be used from the main thread. As noted earlier, <a href="../qtcore/qcoreapplication.html#exec">QCoreApplication::exec</a>() must also be called from that thread.</p>
<p>In practice, the impossibility of using GUI classes in other threads than the main thread can easily be worked around by putting time-consuming operations in a separate worker thread and displaying the results on screen in the main thread when the worker thread is finished. This is the approach used for implementing the <a href="../qtcore/qtcore-threads-mandelbrot-example.html">Mandelbrot Example</a> and the <a href="../qtnetwork/qtnetwork-blockingfortuneclient-example.html">Blocking Fortune Client Example</a>.</p>
<p>In general, creating <a href="../qtwebkit/qtwebkit-bridge.html#qobjects">QObjects</a> before the <a href="../qtwidgets/qapplication.html">QApplication</a> is not supported and can lead to weird crashes on exit, depending on the platform. This means static instances of <a href="../qtcore/qobject.html">QObject</a> are also not supported. A properly structured single or multi-threaded application should make the <a href="../qtwidgets/qapplication.html">QApplication</a> be the first created, and last destroyed <a href="../qtcore/qobject.html">QObject</a>.</p>
<a name="per-thread-event-loop"></a>
<h2 id="per-thread-event-loop">Per-Thread Event Loop</h2>
<p>Each thread can have its own event loop. The initial thread starts its event loop using <a href="../qtcore/qcoreapplication.html#exec">QCoreApplication::exec</a>(), or for single-dialog GUI applications, sometimes <a href="../qtwidgets/qdialog.html#exec">QDialog::exec</a>(). Other threads can start an event loop using <a href="../qtcore/qthread.html#exec">QThread::exec</a>(). Like <a href="../qtcore/qcoreapplication.html">QCoreApplication</a>, <a href="../qtcore/qthread.html">QThread</a> provides an <a href="../qtcore/qthread.html#exit">exit</a>(int) function and a <a href="../qtcore/qthread.html#quit">quit()</a> slot.</p>
<p>An event loop in a thread makes it possible for the thread to use certain non-GUI Qt classes that require the presence of an event loop (such as <a href="../qtcore/qtimer.html">QTimer</a>, <a href="../qtnetwork/qtcpsocket.html">QTcpSocket</a>, and <a href="../qtcore/qprocess.html">QProcess</a>). It also makes it possible to connect signals from any threads to slots of a specific thread. This is explained in more detail in the <a href="threads-qobject.html#signals-and-slots-across-threads">Signals and Slots Across Threads</a> section below.</p>
<p class="centerAlign"><img src="images/threadsandobjects.png" alt="Threads, objects, and event loops" /></p><p>A <a href="../qtcore/qobject.html">QObject</a> instance is said to <i>live</i> in the thread in which it is created. Events to that object are dispatched by that thread's event loop. The thread in which a <a href="../qtcore/qobject.html">QObject</a> lives is available using <a href="../qtcore/qobject.html#thread">QObject::thread</a>().</p>
<p>The <a href="../qtcore/qobject.html#moveToThread">QObject::moveToThread</a>() function changes the thread affinity for an object and its children (the object cannot be moved if it has a parent).</p>
<p>Calling <code>delete</code> on a <a href="../qtcore/qobject.html">QObject</a> from a thread other than the one that <i>owns</i> the object (or accessing the object in other ways) is unsafe, unless you guarantee that the object isn't processing events at that moment. Use <a href="../qtcore/qobject.html#deleteLater">QObject::deleteLater</a>() instead, and a <a href="../qtcore/qevent.html#Type-enum">DeferredDelete</a> event will be posted, which the event loop of the object's thread will eventually pick up. By default, the thread that <i>owns</i> a <a href="../qtcore/qobject.html">QObject</a> is the thread that <i>creates</i> the <a href="../qtcore/qobject.html">QObject</a>, but not after <a href="../qtcore/qobject.html#moveToThread">QObject::moveToThread</a>() has been called.</p>
<p>If no event loop is running, events won't be delivered to the object. For example, if you create a <a href="../qtcore/qtimer.html">QTimer</a> object in a thread but never call <a href="../qtcore/qthread.html#exec">exec()</a>, the <a href="../qtcore/qtimer.html">QTimer</a> will never emit its <a href="../qtcore/qtimer.html#timeout">timeout()</a> signal. Calling <a href="../qtcore/qobject.html#deleteLater">deleteLater()</a> won't work either. (These restrictions apply to the main thread as well.)</p>
<p>You can manually post events to any object in any thread at any time using the thread-safe function <a href="../qtcore/qcoreapplication.html#postEvent">QCoreApplication::postEvent</a>(). The events will automatically be dispatched by the event loop of the thread where the object was created.</p>
<p>Event filters are supported in all threads, with the restriction that the monitoring object must live in the same thread as the monitored object. Similarly, <a href="../qtcore/qcoreapplication.html#sendEvent">QCoreApplication::sendEvent</a>() (unlike <a href="../qtcore/qcoreapplication.html#postEvent">postEvent()</a>) can only be used to dispatch events to objects living in the thread from which the function is called.</p>
<a name="accessing-qobject-subclasses-from-other-threads"></a>
<h2 id="accessing-qobject-subclasses-from-other-threads">Accessing QObject Subclasses from Other Threads</h2>
<p><a href="../qtcore/qobject.html">QObject</a> and all of its subclasses are not thread-safe. This includes the entire event delivery system. It is important to keep in mind that the event loop may be delivering events to your <a href="../qtcore/qobject.html">QObject</a> subclass while you are accessing the object from another thread.</p>
<p>If you are calling a function on an <a href="../qtcore/qobject.html">QObject</a> subclass that doesn't live in the current thread and the object might receive events, you must protect all access to your <a href="../qtcore/qobject.html">QObject</a> subclass's internal data with a mutex; otherwise, you may experience crashes or other undesired behavior.</p>
<p>Like other objects, <a href="../qtcore/qthread.html">QThread</a> objects live in the thread where the object was created -- <i>not</i> in the thread that is created when <a href="../qtcore/qthread.html#run">QThread::run</a>() is called. It is generally unsafe to provide slots in your <a href="../qtcore/qthread.html">QThread</a> subclass, unless you protect the member variables with a mutex.</p>
<p>On the other hand, you can safely emit signals from your <a href="../qtcore/qthread.html#run">QThread::run</a>() implementation, because signal emission is thread-safe.</p>
<a name="signals-and-slots-across-threads"></a>
<h2 id="signals-and-slots-across-threads">Signals and Slots Across Threads</h2>
<p>Qt supports these signal-slot connection types:</p>
<ul>
<li><a href="../qtcore/qt.html#ConnectionType-enum">Auto Connection</a> (default) If the signal is emitted in the thread which the receiving object has affinity then the behavior is the same as the Direct Connection. Otherwise, the behavior is the same as the Queued Connection."</li>
<li><a href="../qtcore/qt.html#ConnectionType-enum">Direct Connection</a> The slot is invoked immediately, when the signal is emitted. The slot is executed in the emitter's thread, which is not necessarily the receiver's thread.</li>
<li><a href="../qtcore/qt.html#ConnectionType-enum">Queued Connection</a> The slot is invoked when control returns to the event loop of the receiver's thread. The slot is executed in the receiver's thread.</li>
<li><a href="../qtcore/qt.html#ConnectionType-enum">Blocking Queued Connection</a> The slot is invoked as for the Queued Connection, except the current thread blocks until the slot returns.<p><b>Note: </b>Using this type to connect objects in the same thread will cause deadlock.</p></li>
<li><a href="../qtcore/qt.html#ConnectionType-enum">Unique Connection</a> The behavior is the same as the Auto Connection, but the connection is made only if it does not duplicate an existing connection. i.e., if the same signal is already connected to the same slot for the same pair of objects, then the connection is not made and connect() returns <code>false</code>.</li>
</ul>
<p>The connection type can be specified by passing an additional argument to <a href="../qtcore/qobject.html#connect-4">connect()</a>. Be aware that using direct connections when the sender and receiver live in different threads is unsafe if an event loop is running in the receiver's thread, for the same reason that calling any function on an object living in another thread is unsafe.</p>
<p><a href="../qtcore/qobject.html#connect-4">QObject::connect</a>() itself is thread-safe.</p>
<p>The <a href="../qtcore/qtcore-threads-mandelbrot-example.html">Mandelbrot Example</a> uses a queued connection to communicate between a worker thread and the main thread. To avoid freezing the main thread's event loop (and, as a consequence, the application's user interface), all the Mandelbrot fractal computation is done in a separate worker thread. The thread emits a signal when it is done rendering the fractal.</p>
<p>Similarly, the <a href="../qtnetwork/qtnetwork-blockingfortuneclient-example.html">Blocking Fortune Client Example</a> uses a separate thread for communicating with a TCP server asynchronously.</p>
</div>
<!-- @@@threads-qobject.html -->
<p class="naviNextPrevious footerNavi">
<a class="prevPage" href="threads-reentrancy.html">Reentrancy and Thread-Safety</a>
<span class="naviSeparator"> ◦ </span>
<a class="nextPage" href="threads-modules.html">Thread-Support in Qt Modules</a>
</p>
</div>
</div>
</div>
</div>
</div>
<div class="footer">
<p>
<acronym title="Copyright">©</acronym> 2017 The Qt Company Ltd.
Documentation contributions included herein are the copyrights of
their respective owners.<br> The documentation provided herein is licensed under the terms of the <a href="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation License version 1.3</a> as published by the Free Software Foundation.<br> Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property
of their respective owners. </p>
</div>
</body>
</html>
|