On Thursday, 3 March 2022 23:32:11 PST Tobias Leupold wrote:
> I did it like this. I created one strace for the scanner not causing
> problems and scanned two pages. This resulted in 27,096 lines of output.
>
> Then I created one for the scanner causing the issue, also scanning two
> pages. This y
On Friday, 4 March 2022 09:02:37 PST Thiago Macieira wrote:
> > I uploaded the traces here:
> > https://l3u.de/tmp/strace_brscan.txt.xz
> > https://l3u.de/tmp/strace_plustek.txt.xz
> >
> > Thanks again for all help!
>
> I'll take a look. Let's see... the brscan trace doesn't have any use of
> PID
Hey Thiago,
Am Freitag, 4. März 2022, 18:35:23 CET schrieb Thiago Macieira:
> And this is the reason why you got the symptom of QProcess breaking. We'd
> have expected that the eight mention be the same as the fifth, to keep the
> pattern going, but it isn't. It's the same as the second and sixth
On Friday, 4 March 2022 10:52:00 PST Tobias Leupold wrote:
> I simply made this a QObject subclass and rather then using start() etc.
> directly, I created a QProcess object and did the same stuff with this one.
>
> No freezes anymore. No matter what scanner I use.
>
> I never thought subclassing
We are pleased to announce that CMake 3.21.6 is now available for
download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
Changes made since CMake 3.21.5:
We are pleased to announce that CMake 3.22.3 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
Changes made since CMake 3.22.2:
> It's a side-effect. The problem is the QProcess::setupChildProcess virtual
> in Qt 5, that had been there since QProcess was introduced the the
> Paleolithic Era. When we use CLONE_PIDFD, we have to call clone() directly,
> which means the hooks installed by pthread_atfork() do not get run. In
>
On Friday, 4 March 2022 13:47:07 PST Tobias Leupold wrote:
> I don't know if this would be still possible for the Qt 5 docs, but a small
> hint like "If you subclass this, be aware that ..." woudn't hurt ... As
> said, I would never have thought that this would have such side-effects!
It shouldn't
