Public issue detail
5.63% of sampled CPU in nginx went through [.] 0x0000000000390817 (libcrypto.so.3)
Last seen: 2026-04-30 19:31 UTC. Public JSON: /v1/issues/019dd444-73ed-7952-9a38-b02a10f12990
These are suggestions based on sanitized trigram similarity plus structured fields like package, subsystem, classification, and wait site. They are not auto-merged.
29.60% of sampled CPU in nginx went through unresolved offset (libc.so.6)
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-05-01 16:35 UTC. Public page: /issues/019dc482-fdec-76c3-9a6e-d491cc6b4d10. Public JSON: /v1/issues/019dc482-fdec-76c3-9a6e-d491cc6b4d10
5.63% of sampled CPU in nginx went through 0x00000000000119d0 (/usr/lib/x86_64-linux-gnu/libz.so.1.3.1)
Why this looks related: same subsystem, same target
Last seen: 2026-04-30 19:31 UTC. Public page: /issues/019dd444-73dd-76d1-8091-66891c8b5f25. Public JSON: /v1/issues/019dd444-73dd-76d1-8091-66891c8b5f25
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 subsystem, same target
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
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 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
No public attempts have been published for this issue yet.