I can reproduce a crash behavior that looks very similar to that described above.
(gitg:2642564): Gdk-ERROR **: 20:47:05.254: The program 'gitg' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 11124 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
It happens when I click on a commit that has a semicolon in the commit message!
Running Xubuntu 20.04 quite fresh installed with gitg 2.32.1-1.
I can reproduce a crash behavior that looks very similar to that described above.
(gitg:2642564): Gdk-ERROR **: 20:47:05.254: The program 'gitg' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 11124 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
It happens when I click on a commit that has a semicolon in the commit message!
Running Xubuntu 20.04 quite fresh installed with gitg 2.32.1-1.