Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Core dumped, continually #2498

Open
Gerrit15 opened this issue Jan 22, 2025 · 3 comments
Open

Core dumped, continually #2498

Gerrit15 opened this issue Jan 22, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@Gerrit15
Copy link

Describe the bug
When I attempt to open gitui I get this error:

GitUI was close due to an unexpected panic.
Please file an issue on https://github.com/extrawurst/gitui/issues with the following info:

PanicHookInfo { payload: Any { .. }, location: Location { file: "asyncgit/src/revlog.rs", line: 186, col: 14 }, can_unwind: true, force_no_backtrace: false }
trace:
0:
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:

GitUI was close due to an unexpected panic.
Please file an issue on https://github.com/extrawurst/gitui/issues with the following info:

Any { .. }
trace:
0:
1:
2:
3:
4:
5:
6:
7:

zsh: IOT instruction (core dumped) gitui

To Reproduce
Unsure, honestly. It started at one point for no particular reason I can tell, and it has continued- even after upgrade, reboot, re-opening terminal

Expected behavior
It happens as soon as I try to open gitui from the command line

Context (please complete the following information):

  • OS/Distro + Version: Arch Linux, most recent
  • GitUI Version: most recent
  • Rust version: most recent
  • terminal: alacritty
  • shell: zs
@Gerrit15 Gerrit15 added the bug Something isn't working label Jan 22, 2025
@extrawurst
Copy link
Owner

do you have a repo i can try to reproduce this on?

@Gerrit15
Copy link
Author

Apologies, I cannot provide the repo that I was originally using it on, as it was college assignment. I can say however that it was happening on every repo I could check it on. Though if it helps, it has 'resolved' itself, and when it did reopen it was on the log, which is a feature I tend not to use.

@extrawurst
Copy link
Owner

If you ever have a repo that’s public where this happens please let me know

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants