gitg crashed with SIGABRT in g_slice_free_chain_with_offset()

Bug #1090283 reported by markusj
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gitg (Ubuntu)
New
Undecided
Unassigned

Bug Description

The crash happened for no specific reason. The repository which had been opened with gitg has changed (pushed a commit to a remote repo).

gitg crashes quite often if the opened repository changes ...

Edit: Sorry, i had to delete the core dump, it contained too much private data, which should have been erased out of memory shutdowns/reboots ago. I have no idea why this data has been still there.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gitg 0.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
Uname: Linux 3.2.0-34-generic x86_64
ApportVersion: 2.0.1-0ubuntu15
Architecture: amd64
Date: Fri Dec 14 10:30:51 2012
ExecutablePath: /usr/bin/gitg
MarkForUpload: True
ProcCmdline: gitg
Signal: 6
SourcePackage: gitg
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_free_chain_with_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gitg crashed with SIGABRT in g_slice_free_chain_with_offset()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip fuse lpadmin netdev plugdev public-share sambashare scanner sudo vboxusers video

Revision history for this message
markusj (markusj) wrote :
tags: removed: need-amd64-retrace
markusj (markusj)
description: updated
information type: Private → Public
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.