BePDF KDLs on exit

[kvdman]

Testing BePDF on Haiku, it will crash inconsistently when exiting the application. You'll see when you close it (if it doesn't KDL), that it is still running in the taskbar. If you try and kill it with process controller you'll KDL as well. This was testing without reading any file, and appears to be new as of one week... See attached.

[kvdman]

I should add, Haiku hrev28544, BePDF 1.1.1.

[anevilyak]

(In #3588) Indeed, thanks!

[stippi]

I haven't seen BePDF KDL on exit, but it consistently "hangs". That is, it's actually still functional, because you can double click PDFs and they will open in BePDF. I think it's still the same instance.

The hang is caused by the main application thread waiting for the two "OutputTracer" threads. These are apparently supposed to log stdio and stderr output (of xpdf?). Both of these threads are blocking in the respective read() call. I think what happens is that the stdio/stderr file descriptors are not being deleted at this point in time, and BePDF makes a wrong assumption about the order in which the teardown happens on program exit. Or BePDF is correct and there is a bug in Haiku. To investigate, just hit F12, type "teams", find the BePDF team, type "threads #BePDF team id#", and type "sc #each thread id#" to see the "deadlock".

[modeenf]

I tested to start and close BePDF in hrev31406 and I hade no problem.Can I close this one?

[kvdman]

Seems resolved, please do.