El martes, 16 de mayo de 2023 16:12:36 -03 Thiago Macieira escribió:
> On Monday, 15 May 2023 21:23:21 PDT Thiago Macieira wrote:
> > We still don't know why this happened because all our attempts
> > to find out why cause the problem to disappear.
>
> BTW, we found that the user's application was
El martes, 16 de mayo de 2023 16:12:36 -03 Thiago Macieira escribió:
> On Monday, 15 May 2023 21:23:21 PDT Thiago Macieira wrote:
> > We still don't know why this happened because all our attempts
> > to find out why cause the problem to disappear.
>
> BTW, we found that the user's application was
On Monday, 15 May 2023 21:23:21 PDT Thiago Macieira wrote:
> We still don't know why this happened because all our attempts
> to find out why cause the problem to disappear.
BTW, we found that the user's application was linking against
libKF5NetworkManagerQt, not KF6, because they were using an i
I've been trying to help someone in Slack[1] with a heisenbug that a Qt-based
application ended up deadlocking only when run with QProcess. After some
debugging, we've found out that both Qt5 and Qt6 libraries are loaded in the
same process. We still don't know why this happened because all our
