Public issue detail
1.24% of sampled CPU in python3.13 went through 0x00000000001ec533 (/usr/lib/x86_64-linux-gnu/libcrypto.so.3)
Last seen: 2026-04-29 13:39 UTC. Public JSON: /v1/issues/019dd21c-9ed1-7901-9ad4-49910b757796
These are suggestions based on sanitized trigram similarity plus structured fields like package, subsystem, classification, and wait site. They are not auto-merged.
4.12% of sampled CPU in postgres went through unresolved offset (/usr/lib/x86_64-linux-gnu/libcrypto.so.3)
Why this looks related: same package, same source package, same subsystem
Last seen: 2026-05-01 06:11 UTC. Public page: /issues/019dda3f-67ae-71d3-b1a8-1623e30510d4. Public JSON: /v1/issues/019dda3f-67ae-71d3-b1a8-1623e30510d4
29.60% of sampled CPU in nginx went through unresolved offset (/usr/lib/x86_64-linux-gnu/libssl.so.3)
Why this looks related: same package, same source package, same subsystem
Last seen: 2026-05-01 16:35 UTC. Public page: /issues/019dc8fe-0c52-7a90-9d3b-15e131b0803c. Public JSON: /v1/issues/019dc8fe-0c52-7a90-9d3b-15e131b0803c
3.96% of sampled CPU in postgres went through DSO_free (/usr/lib/x86_64-linux-gnu/libcrypto.so.3)
Why this looks related: same package, same source package, same subsystem
Last seen: 2026-05-01 09:37 UTC. Public page: /issues/019de2e6-1c58-7b83-8edc-ca9feafa0ae8. Public JSON: /v1/issues/019de2e6-1c58-7b83-8edc-ca9feafa0ae8
4.18% of sampled CPU in postgres went through OPENSSL_LH_flush (/usr/lib/x86_64-linux-gnu/libcrypto.so.3)
Why this looks related: same package, same source package, same subsystem
Last seen: 2026-04-29 05:56 UTC. Public page: /issues/019dd7bb-8ab4-7000-9c69-c101b194377d. Public JSON: /v1/issues/019dd7bb-8ab4-7000-9c69-c101b194377d
5.51% of sampled CPU in python3.13 went through unresolved offset (/usr/bin/python3.13)
Why this looks related: same subsystem, same target
Last seen: 2026-05-01 07:26 UTC. Public page: /issues/019dda71-4986-77f3-ae4a-ed6e5a255180. Public JSON: /v1/issues/019dda71-4986-77f3-ae4a-ed6e5a255180
2.47% of sampled CPU in python3.13 went through unresolved offset (mandb)
Why this looks related: same subsystem, same target
Last seen: 2026-04-30 04:50 UTC. Public page: /issues/019ddcb9-ae53-7bb2-8fe4-e5e72e6954ba. Public JSON: /v1/issues/019ddcb9-ae53-7bb2-8fe4-e5e72e6954ba
No public attempts have been published for this issue yet.