[Bug]: Helium browser getting terminated with SIGBUS when trying to access some profile
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- desktop-dev
Research direction
The report gives a reproducible path (open Helium, select the affected profile) and confirms a fresh --user-data-dir profile does not trigger it, so the fault is tied to state in that specific profile rather than to the build. Start by reading the six-comment thread to see whether maintainers already narrowed it to a component, then reproduce under a debugger or check the crash log for the faulting library and offset. SIGBUS on a misaligned address usually points at a memory-mapped file in the profile directory, so 'done' means identifying which file and code path faults and confirming the fix no longer crashes on that profile.
Written by the indexing model from the issue text.
Description
Version
Version 0.19.2.1 (Official Build, Chromium 155.0.8059.39) Arch Linux (x86_64)
Have you tested that this is not an upstream issue or an issue with your configuration?
- I have tried reproducing this issue in Chrome and it could not be reproduced there
- I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there
- I have tried reproducing this issue in Helium with a new and empty profile using
--user-data-dircommand line argument and it could not be reproduced there
Description
Helium getting terminated with SIGBUS (Misaligned address error) when accessing some profile
How to Reproduce?
- Open helium
- Press any profile
Actual behavior
Helium crashes on choosing some profile
Expected behavior
Helium opens said profile
Additional context
https://github.com/user-attachments/assets/24975fb8-aa94-4717-8151-27c512718df3
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 63
- Avg merge
- 28m
- Merged PRs (30d)
- 11
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from imputnet/helium-linux
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
imputnet/helium-linux#385 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#459 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
imputnet/helium-linux#457 ·
Maintainers usually reply within 1 day
-
feat
Difficulty 3/5 1-2 days Newbie friendliness 48/100
imputnet/helium-linux#455 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#454 ·
Maintainers usually reply within 1 day
All issues in imputnet/helium-linux
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
varnish/helm-varnish#173 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
GameServerManagers/LinuxGSM#5242 ·
Maintainers usually reply within 1 day
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days