mirror of
https://github.com/imputnet/helium.git
synced 2026-11-17 18:59:24 +00:00
[Bug]: Renderer crashes with SIGILL (deliberate CHECK trap) on 'Empty cache and hard reload' (Linux, 0.21.2.1) #2927
Labels
No labels
approved
approved
approved
bad ux
bot:review
bot:size
bug
bug
bug
can't replicate
can't replicate
can't replicate
confirmed
confirmed
confirmed
external
feat
feat
feat
good first issue
good first issue
good first issue
invalid
invalid
invalid
needs more info
needs more info
needs more info
pending
pending
pending
upstream
upstream
upstream
WAI
WAI
WAI
wontfix
wontfix
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
imputnet/helium#2927
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Operating system
Arch Linux x86_64 (kernel 7.2.15), Wayland (Hyprland), AMD Ryzen 5 5600G, root on btrfs over LUKS.
Version
0.21.2.1 (Chromium 157.0.8103.50), official Linux x86_64 build (AUR
helium-browser-bin0.21.2.1-1)Also re-tested on 0.21.3.1 (Chromium 157.0.8103.78) — see "Additional context" for what happens there.
Have you tested that this is not an upstream issue or an issue with your configuration?
--user-data-dircommand line argument and it could not be reproduced thereNot yet — happy to run these comparisons on request. Filing now because the crash is fully deterministic on my machine (3/3 attempts) and the core-dump forensics below show it is an in-binary
CHECKfailure trap, not a config/environment issue.Description
Using the reload-button context-menu item "Empty cache and hard reload" deterministically kills the tab's renderer process with SIGILL. It reproduced 3 out of 3 times in a single session (Nov 14, 19:10 / 19:13 / 19:15), always at the same instruction.
Crash ID
None — no crashpad report was retained for these crashes (the
Crash Reportsdirectory only contains an unrelated report from October). The crashes were captured by systemd-coredump instead; I can share the compressed core,coredumpctl infooutput, or gdb output from it if that helps.How to Reproduce?
Actual behavior
All three renderer processes died with
SIGILL,si_code: ILL_ILLOPN, at the identical instruction pointer (renderers fork from the same zygote, so the load base is constant):The crashing process is
--type=renderer:Forensics (I kept the 0.21.2.1 package and analyzed the core):
0xC1A5E38in the 0.21.2.1 binary (ELF file offset0xC1A4E38).ud2— the compiler's encoding of a deliberate crash (IMMEDIATE_CRASH()after a failedCHECK). So this is an intentional renderer-side CHECK failure, not a stray jump into data and not an unsupported CPU instruction (the CPU is a Ryzen 5 5600G with AVX2, and the faulting page is the binary's own text segment, not JIT memory).ud2at binary offset0xC1A4E38in the 0.21.2.1 Linux x86_64 build.Each crash left a ~9 GB uncompressed core on my machine (large renderer), so the systemd-coredump processing amplified each tab crash into a multi-minute system-wide stall — that part is my distro's coredump configuration, not the browser, but it's why the crash feels like a full system freeze here.
Expected behavior
"Empty cache and hard reload" clears the cache and reloads the page without the renderer dying.
Additional context
ILL_ILLOPN, i.e. the same kind of deliberate trap) with a different trigger.network.mojom.NetworkServiceprocess sustained a write burst of 30–160 MB per 5 seconds for ~4.5 minutes (~2.2 GB total, near-zero reads), keeping the disk at 100% busy and pushing I/O pressure (PSIsome) to 87.9%, which makes the whole desktop unresponsive on my setup (btrfs on LUKS). The profile's cache directory afterwards is only ~14 MB, so most of those writes appear to be rewritten/deleted churn rather than retained cache entries. I'm not claiming this is the same root cause as the 0.21.2.1 crash — reporting the measurement in case it's a useful clue about what the cache-clear path is doing.--ozone-platform=wayland; GPU is the Radeon iGPU of the 5600G (amdgpu); 14 GB RAM; crash times and journal excerpts above are fromjournalctl -k.