Victor

> Possibly fixed by [85e9706](https://github.com/Perl/perl5/commit/85e97066288fa0be7b08897c6306e33ea2ef45d7) So you're suggesting that the Oracle instant client lib starts one or more additional non Perl threads that may leak into Perl land causing mayhem?...

> It's only a problem when you mix library worker threads with signals. > > Your backtrace: > > ``` > #6 0x00007fffeeff1ec9 in kpucpincrtime () from /usr/lib/oracle/23/client64/lib/libclntsh.so.23.1 > #7...

> [@tonycoz](https://github.com/tonycoz), is this a perl problem or a DBD-Oracle problem? If the latter, then we should direct the OP to a more appropriate place to file this bug report....

I have tested the patch placed in "bleed" (mentioned above) that forces Perl "WOOL' on to the non-Perl thread and then allows it to continue to handle the interrupt. I've...

The example I used was something I made up (the alternative) simply to convey the intent not the final code. I'll have another look and if there is a bleed...

I think you believe this test shows that the child is using the same thread as the parent. Not possible. No amount of looking at thread id compares will change...