Segfault in libpthread after auto updating Jackett

Jackett was auto updated and a segfault appeared in logs:

Oct 24 02:07:54 Orthanc Docker Auto Update: Stopping jackett
Oct 24 02:07:54 Orthanc kernel: jackett[15933]: segfault at 10 ip 000015497d9b8fa0 sp 00007ffcf94158d8 error 4 in libpthread-2.27.so[15497d9af000+1a000]
Oct 24 02:07:54 Orthanc kernel: Code: 07 00 00 00 48 89 df b8 ca 00 00 00 0f 05 64 48 c7 04 25 f0 02 00 00 00 00 00 00 b8 83 00 00 00 e9 a8 fb ff ff 0f 1f 44 00 00 <8b> 47 10 89 c2 81 e2 7f 01 00 00 90 83 e0 7c 0f 85 9b 00 00 00 48
Oct 24 02:07:57 Orthanc kernel: veth13798ed: renamed from eth0
Oct 24 02:07:57 Orthanc kernel: br-d45ab5905980: port 10(veth98599ed) entered disabled state
Oct 24 02:07:57 Orthanc kernel: br-d45ab5905980: port 10(veth98599ed) entered disabled state
Oct 24 02:07:57 Orthanc kernel: device veth98599ed left promiscuous mode
Oct 24 02:07:57 Orthanc kernel: br-d45ab5905980: port 10(veth98599ed) entered disabled state
Oct 24 02:07:57 Orthanc Docker Auto Update: Stopping lidarr
Oct 24 02:08:01 Orthanc kernel: veth3683ba0: renamed from eth0
Oct 24 02:08:01 Orthanc kernel: br-d45ab5905980: port 5(vethd40c869) entered disabled state

Everything works fine (as far as I can tell), but I'm worried about seeing a segfault on the logs. Anybody knows what could be happening?

Attached diagnostics

orthanc-diagnostics-20191024-0547.zip