gitg launches, renders its window, hands, and segfaults

[Christopher Barrington-Leigh]

The first time I tried using gitg, it launched and was immediately unresponsive. Eventually it died.

Now whenever I launch it in that same folder, it renders and then immediately dies. Here is what is left in the terminal:

(gitg:20945): Gdk-ERROR **: 18:56:08.453: 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 7817 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.)
Trace/breakpoint trap (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gitg 3.32.1-1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 20 18:43:26 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-01-24 (452 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gitg
UpgradeStatus: Upgraded to eoan on 2019-10-31 (172 days ago)

[Christopher Barrington-Leigh (cpbl)]

I tried this in gdb too:

$ gdb gitg
GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gitg...
(No debugging symbols found in gitg)
(gdb) run
Starting program: /usr/bin/gitg
[Thread debugging using libthread_db enabled]

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff2c3e700 (LWP 27955)]
[New Thread 0x7ffff243d700 (LWP 27956)]
[New Thread 0x7ffff1aee700 (LWP 27957)]
[New Thread 0x7ffff0f2a700 (LWP 27958)]
[New Thread 0x7fffe3fff700 (LWP 27959)]
[New Thread 0x7fffe37fe700 (LWP 27961)]
[New Thread 0x7fffe2ffd700 (LWP 27962)]
[New Thread 0x7fffe2345700 (LWP 27963)]
[New Thread 0x7fffe1b44700 (LWP 27964)]
[Thread 0x7fffe1b44700 (LWP 27964) exited]
[Thread 0x7fffe2ffd700 (LWP 27962) exited]
[Thread 0x7fffe37fe700 (LWP 27961) exited]
[Thread 0x7fffe3fff700 (LWP 27959) exited]

(gitg:27951): Gdk-ERROR **: 19:27:43.445: 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 9454 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.)

Thread 1 "gitg" received signal SIGTRAP, Trace/breakpoint trap.
0x00007ffff7d79955 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0 0x00007ffff7d79955 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00007ffff7d7c32c in g_log_writer_default () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff7d7a597 in g_log_structured_array () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007ffff7d7afb4 in g_log_structured_standard () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007ffff74c7bea in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#5 0x00007ffff74d4bb3 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#6 0x00007ffff66f50db in _XError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
#7 0x00007ffff66f1e47 in () at /usr/lib/x86_64-linux-gnu/libX11.so.6
#8 0x00007ffff66f1ee5 in () at /usr/lib/x86_64-linux-gnu/libX11.so.6
#9 0x00007ffff66f2e6d in _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
#10 0x00007ffff66eff3d in XTranslateCoordinates () at /usr/lib/x86_64-...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Nina Marwede (lynax)]

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.