SEGV crash on refresh of remote accounts
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 10
Description
Distribution: Flatpak
Version: 1.2.0
I tried to refresh my remote account (private hosted gitlab) and gittyup crashed with a segmentation violation without any log message printed. It happened multiple times until i removed and readded the account.
The animation that is shown on the remote account refresh has not started the times it crashed.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the crash in the Flatpak build while refreshing a private hosted GitLab account, noting that no log message or refresh animation appears. Compare the behavior after removing and re-adding the account; done means repeated refreshes no longer cause a segmentation violation and the refresh proceeds normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, gitlab
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100