On Friday 08 January 2016 11:11:11 Etienne Sandré-Chardonnal wrote:
> Could it be that the QTimer is using a different thread, that gets stuck
> due to the high system load?
If you created it in a different thread, then it is using that thread.
--
Thiago Macieira - thiago.macieira (AT) intel.com
On Jan 8, 2016, at 4:11 AM, Etienne Sandré-Chardonnal
mailto:etienne.san...@m4x.org>> wrote:
Dear all,
In a recent stress test, where I created 5 sub-processes, each one starting
idealThreadCount() fully working threads (ie they never sleep), I found that a
QTimer responsible for sending some
Dear all,
In a recent stress test, where I created 5 sub-processes, each one starting
idealThreadCount() fully working threads (ie they never sleep), I found
that a QTimer responsible for sending some information messages to the
sub-process stdout was stuck until the working threads stopped.
The
