gitg crashes, repeatable

Bug #2025692 reported by psl
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gitg (Ubuntu)
New
Undecided
Unassigned

Bug Description

$ gitg --version
gitg 3.32.1

Linux Mint 20.3 amd64

Crash:

user@ubuntu:~/ipfire-2.x$ gitg

(gitg:128632): Gdk-ERROR **: 04:35:02.316: 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 168873 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)

user@ubuntu:~/ipfire-2.x$ gdb gitg
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04.1) 9.2
Copyright (C) 2020 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 0x7ffff291b700 (LWP 128778)]
[New Thread 0x7ffff211a700 (LWP 128779)]
[New Thread 0x7ffff1876700 (LWP 128780)]
[New Thread 0x7ffff0ea3700 (LWP 128781)]
[New Thread 0x7fffdb680700 (LWP 128782)]
[New Thread 0x7fffdae7f700 (LWP 128783)]
[Thread 0x7fffdae7f700 (LWP 128783) exited]
[Thread 0x7ffff0ea3700 (LWP 128781) exited]
[New Thread 0x7ffff0ea3700 (LWP 128784)]
[Thread 0x7ffff0ea3700 (LWP 128784) exited]

(gitg:128774): Gdk-ERROR **: 04:38:50.116: 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 36803 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.
0x00007ffff7d6b295 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0

How to replicate:

user@ubuntu:~$ git clone git://git.ipfire.org/ipfire-2.x.git
user@ubuntu:~$ cd ipfire-2.x
user@ubuntu:~$ gitg

# find commit 955964d7a28150570d2916c59698fa9b83a0a242

$ git log 955964d7a28150570d2916c59698fa9b83a0a242 | head -6
commit 955964d7a28150570d2916c59698fa9b83a0a242
Author: Peter Müller <email address hidden>
Date: Sun Jun 25 20:45:49 2023 +0000

    go: Update aarch64 rootfile

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.