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

Crash on repository with commit changing many files #132

Open
Ecordonnier opened this issue Apr 18, 2023 · 1 comment
Open

Crash on repository with commit changing many files #132

Ecordonnier opened this issue Apr 18, 2023 · 1 comment

Comments

@Ecordonnier
Copy link

Ecordonnier commented Apr 18, 2023

I have a private repository (which I am not allowed to share) where qgit crashes a few seconds after being started. The likely root-cause is that this one commit modifies many files (git reports 28062 files changed, 2362600 insertions(+), 403254 deletions(-)). The UI shows the bottom-right loading bar completion increasing until the crash. I still have 20GB of RAM available on the system at the moment of the crash:

$ qgit c152dcb8a6646a27269a987231fc524031d6c9e7
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted (core dumped)

Which information do you need to reproduce? Is there a log file I can send? Or do you need a full call-stack with debug-symbols?
I think it's related to #125

@tibirna
Copy link
Owner

tibirna commented Apr 20, 2023

Thanks for the report.

Please indicate which version of qgit you are using. (The patch for #125 was not included in the last released version, so it will be interesting to know if you use v2.10 or earlier or perhaps you compiled from latest git master).

If you use a distro-compiled package, please check if the distro provides a "debug" package and install it. Then reproduce the crash again and let's hope you will get a core dump that I can analyse.

If you compile the sources yourself, please consider using the "debug" profile and then try to reproduce the crash.

The bad_alloc error clearly indicates that memory allocation fails at some low level, but only full stack trace will tell me where this happens.

Also, please confirm that you can successfully navigate the repository on your system using the command-line git.

Thanks
Cristian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants