Public issue detail

Crash in chrome: SEGV at libc.so.6

Top frame: n/a [libEGL_nvidia.so.0]

highpackage: google-chrome-stablesource: google-chrome-stablescore: 98reports: 1successful triage

Last seen: 2026-03-29 18:31 UTC. Public JSON: /v1/issues/019d39bb-3671-7203-9ebb-706e5ee6e351

Successful triage

Fixer did not find an honest diff-backed change in this source tree. Instead, it published the current best diagnosis and next steps so repeat sightings can converge on the real owner.

best triagecreated: 2026-03-29 14:36 UTCvalidation: ready

A diagnosis and external handoff were created locally because Fixer could not acquire a patchable workspace for google-chrome-stable.

Likely owner

google-chrome-stable

Reason: workspace-acquisition

Next steps

  • Confirm the hotspot still points at google-chrome-stable with a fresh perf sample before filing the bug.
  • Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
  • Map google-chrome-stable to its owning package or project and file an upstream or distro bug with the summarized evidence.
  • If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Browse successful triage

Technical snapshot

Fixer kept the most informative crashing thread and shows the top stack frames below.

Crashing thread stack trace

  • Process: chrome
  • Signal: SEGV
n/a
libc.so.6

Worker outcome summary

This issue has 10 recorded worker attempts. Only ready diffs and ready triage handoffs get dedicated public boards. Diagnosis-only reports and blocked attempts are summarized here so it is easier to see why work stalled.

10 ready triage handoffs

No ready patch attempts, diagnosis-only reports, failed patch attempts, explained impossible attempts, or other attempt states.

Most common blockers

  • workspace-acquisition (10 attempts)

Published attempts

ready triage handoff

triage

A diagnosis and external handoff were created locally because Fixer could not acquire a patchable workspace for google-chrome-stable.

state: readycreated: 2026-03-29 14:36 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: google-chrome-stable

Reason: workspace-acquisition

  • Confirm the hotspot still points at google-chrome-stable with a fresh perf sample before filing the bug.
  • Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
  • Map google-chrome-stable to its owning package or project and file an upstream or distro bug with the summarized evidence.
  • If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.

ready triage handoff

triage

A diagnosis and external handoff were created locally because Fixer could not acquire a patchable workspace for google-chrome-stable.

state: readycreated: 2026-03-29 14:34 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: google-chrome-stable

Reason: workspace-acquisition

  • Confirm the hotspot still points at google-chrome-stable with a fresh perf sample before filing the bug.
  • Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
  • Map google-chrome-stable to its owning package or project and file an upstream or distro bug with the summarized evidence.
  • If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.

ready triage handoff

triage

A diagnosis and external handoff were created locally because Fixer could not acquire a patchable workspace for google-chrome-stable.

state: readycreated: 2026-03-29 14:31 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: google-chrome-stable

Reason: workspace-acquisition

  • Confirm the hotspot still points at google-chrome-stable with a fresh perf sample before filing the bug.
  • Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
  • Map google-chrome-stable to its owning package or project and file an upstream or distro bug with the summarized evidence.
  • If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.

ready triage handoff

triage

A diagnosis and external handoff were created locally because Fixer could not acquire a patchable workspace for google-chrome-stable.

state: readycreated: 2026-03-29 14:27 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: google-chrome-stable

Reason: workspace-acquisition

  • Confirm the hotspot still points at google-chrome-stable with a fresh perf sample before filing the bug.
  • Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
  • Map google-chrome-stable to its owning package or project and file an upstream or distro bug with the summarized evidence.
  • If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.

ready triage handoff

triage

A diagnosis and external handoff were created locally because Fixer could not acquire a patchable workspace for google-chrome-stable.

state: readycreated: 2026-03-29 14:25 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: google-chrome-stable

Reason: workspace-acquisition

  • Confirm the hotspot still points at google-chrome-stable with a fresh perf sample before filing the bug.
  • Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
  • Map google-chrome-stable to its owning package or project and file an upstream or distro bug with the summarized evidence.
  • If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.

ready triage handoff

triage

A diagnosis and external handoff were created locally because Fixer could not acquire a patchable workspace for google-chrome-stable.

state: readycreated: 2026-03-29 14:20 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: google-chrome-stable

Reason: workspace-acquisition

  • Confirm the hotspot still points at google-chrome-stable with a fresh perf sample before filing the bug.
  • Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
  • Map google-chrome-stable to its owning package or project and file an upstream or distro bug with the summarized evidence.
  • If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.

ready triage handoff

triage

A diagnosis and external handoff were created locally because Fixer could not acquire a patchable workspace for google-chrome-stable.

state: readycreated: 2026-03-29 14:15 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: google-chrome-stable

Reason: workspace-acquisition

  • Confirm the hotspot still points at google-chrome-stable with a fresh perf sample before filing the bug.
  • Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
  • Map google-chrome-stable to its owning package or project and file an upstream or distro bug with the summarized evidence.
  • If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.

ready triage handoff

triage

A diagnosis and external handoff were created locally because Fixer could not acquire a patchable workspace for google-chrome-stable.

state: readycreated: 2026-03-29 14:15 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: google-chrome-stable

Reason: workspace-acquisition

  • Confirm the hotspot still points at google-chrome-stable with a fresh perf sample before filing the bug.
  • Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
  • Map google-chrome-stable to its owning package or project and file an upstream or distro bug with the summarized evidence.
  • If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.

ready triage handoff

triage

A diagnosis and external handoff were created locally because Fixer could not acquire a patchable workspace for google-chrome-stable.

state: readycreated: 2026-03-29 14:14 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: google-chrome-stable

Reason: workspace-acquisition

  • Confirm the hotspot still points at google-chrome-stable with a fresh perf sample before filing the bug.
  • Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
  • Map google-chrome-stable to its owning package or project and file an upstream or distro bug with the summarized evidence.
  • If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.

ready triage handoff

triage

A diagnosis and external handoff were created locally because Fixer could not acquire a patchable workspace for google-chrome-stable.

state: readycreated: 2026-03-29 14:13 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: google-chrome-stable

Reason: workspace-acquisition

  • Confirm the hotspot still points at google-chrome-stable with a fresh perf sample before filing the bug.
  • Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
  • Map google-chrome-stable to its owning package or project and file an upstream or distro bug with the summarized evidence.
  • If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.

Quarantine stays on by default so the public queue is harder to spam.