[Bug]: Helium browser getting terminated with SIGBUS when trying to access some profile

Open
#435 6 comments 0 reactions 0 assignees View on GitHub

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
Tech stack
c, cpp, linux
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

bug
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-dir command 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?
  1. Open helium
  2. 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from imputnet/helium-linux

All issues in imputnet/helium-linux

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.