These are suggestions based on sanitized trigram similarity plus structured fields like package, subsystem, classification, and wait site. They are not auto-merged.
cc1 is stuck in a likely unclassified userspace loop: 2.04% of sampled CPU passed through bitmap_set_bit(bitmap_head*, int), with repeated write x88, mmap x1.
highscore: 106reports: 1similarity: 75%
Why this looks related: same classification, same subsystem, same wait site
Last seen: 2026-10-13 06:02 UTC. Public page: /issues/019fa11d-a82b-79e0-891c-85e9b734e4a0. Public JSON: /v1/issues/019fa11d-a82b-79e0-891c-85e9b734e4a0
clang is stuck in a likely unclassified userspace loop: 1.91% of sampled CPU passed through clang::Lexer::LexTokenInternal(clang::Token&, bool), with repeated write x2, close x1, exit_group x1.
highscore: 106reports: 1similarity: 71%
Why this looks related: same classification, same subsystem, same wait site
Last seen: 2026-10-20 04:50 UTC. Public page: /issues/019ff123-7d66-7253-bc62-d7ba8c5bd3e8. Public JSON: /v1/issues/019ff123-7d66-7253-bc62-d7ba8c5bd3e8
llama-server is stuck in a likely unclassified userspace loop: 23.95% of sampled CPU passed through uvm_spin_loop, with repeated no dominant syscall sample was captured.
highscore: 106reports: 1similarity: 69%
Why this looks related: same classification, same subsystem, same wait site
Last seen: 2026-10-22 21:00 UTC. Public page: /issues/01a0b753-7de3-74d2-bfee-879445fd371b. Public JSON: /v1/issues/01a0b753-7de3-74d2-bfee-879445fd371b
lto1 is stuck in a likely unclassified userspace loop: 2.51% of sampled CPU passed through bitmap_set_bit(bitmap_head*, int), with repeated thread backtraces show 1 thread(s) around 0x000000000162a9f7 in constrain_operands(int, unsigned long) ().
highscore: 106reports: 1similarity: 66%
Why this looks related: same classification, same subsystem, same wait site
Last seen: 2026-09-30 11:46 UTC. Public page: /issues/019fa772-cf3b-7890-82d2-60e7dba39362. Public JSON: /v1/issues/019fa772-cf3b-7890-82d2-60e7dba39362
pdftex is stuck in a likely file not found retry loop: 16.24% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x0000559cf35425aa in ?? ().
highscore: 106reports: 1similarity: 53%
Why this looks related: same subsystem, same wait site
Last seen: 2026-10-02 09:54 UTC. Public page: /issues/019f76fe-e585-7490-a51d-2e41820f45d3. Public JSON: /v1/issues/019f76fe-e585-7490-a51d-2e41820f45d3