Public issue detail
16.35% of sampled CPU in python3.13 went through _PyLong_Multiply (/usr/bin/python3.13)
Last seen: 2026-04-29 18:36 UTC. Public JSON: /v1/issues/019dda71-497f-7a91-9d71-4a9eca487e15
These are suggestions based on sanitized trigram similarity plus structured fields like package, subsystem, classification, and wait site. They are not auto-merged.
28.76% of sampled CPU in python3.13 went through _PyLong_New (/usr/bin/python3.13)
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-04-29 17:39 UTC. Public page: /issues/019dda03-7bb1-7112-afa3-200d37f715a5. Public JSON: /v1/issues/019dda03-7bb1-7112-afa3-200d37f715a5
28.76% of sampled CPU in python3.13 went through PyEval_SaveThread (/usr/bin/python3.13)
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-04-29 17:39 UTC. Public page: /issues/019dda03-7bc2-7041-bf88-77a580c3cf48. Public JSON: /v1/issues/019dda03-7bc2-7041-bf88-77a580c3cf48
22.73% of sampled CPU in python3.13 went through _PyEval_EvalFrameDefault (/usr/bin/python3.13)
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-05-01 06:11 UTC. Public page: /issues/019dda71-4996-7c31-832d-e3a1eac9df8c. Public JSON: /v1/issues/019dda71-4996-7c31-832d-e3a1eac9df8c
5.87% of sampled CPU in python3.13 went through _PyObject_MakeTpCall (/usr/bin/python3.13)
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-05-01 06:11 UTC. Public page: /issues/019de229-c678-7122-bfc0-0f61ff92fc18. Public JSON: /v1/issues/019de229-c678-7122-bfc0-0f61ff92fc18
5.51% of sampled CPU in python3.13 went through unresolved offset (/usr/bin/python3.13)
Why this looks related: same package, same source package, 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 package, same source package, 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.