On Wednesday, October 21, 2015 03:15:38 AM Robert Griebl wrote:
> On 20.10.2015 17:56, Thiago Macieira wrote:
> > ...because the application will unload the libraries while other threads
> > are still running code from those threads. In the bug report, the crash
> > happens because of the QXcbEvent
2015-10-21 4:15 GMT+03:00 Robert Griebl :
> On 20.10.2015 17:56, Thiago Macieira wrote:
>> ...because the application will unload the libraries while other threads are
>> still running code from those threads. In the bug report, the crash happens
>> because of the QXcbEventReader thread, but it cou
On 20.10.2015 17:56, Thiago Macieira wrote:
> ...because the application will unload the libraries while other threads are
> still running code from those threads. In the bug report, the crash happens
> because of the QXcbEventReader thread, but it could have been any other thread
> we start or any
On Tuesday 20 October 2015 23:51:12 Marc Mutz wrote:
> On Tuesday 20 October 2015 17:56:33 Thiago Macieira wrote:
> > Can anyone think of a solution to this problem?
>
> Don't call ::exit()? I'm only half-joking. Who calls ::exit() in a C++
> program (apart from implicitly by leaving main())?
The
On Tuesday 20 October 2015 17:56:33 Thiago Macieira wrote:
> Can anyone think of a solution to this problem?
Don't call ::exit()? I'm only half-joking. Who calls ::exit() in a C++ program
(apart from implicitly by leaving main())?
Wild guess: maybe std::terminate() works better?
--
Marc Mutz
...because the application will unload the libraries while other threads are
still running code from those threads. In the bug report, the crash happens
because of the QXcbEventReader thread, but it could have been any other thread
we start or any other library starts.
Can anyone think of a sol
