gedit crashed with SIGSEGV in gd_tagged_entry_remove_tag() when closing a file or searching through the text of one

Bug #1705287 reported by Thomas A. F. Thorne
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
New
Medium
Unassigned

Bug Description

I had large number of files open (more than a dozen) and was searching through each one for test to replace. I was saving and closing each file after I had finished my editing. Then I would select the next file to work on from the top tab bar.

I had two Gedit windows open. One of them only a had a single file in it.

Both gedit windows turned grey, eventually close and then the crash report was posted.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gedit 3.18.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jul 19 16:02:04 2017
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2015-03-12 (859 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
ProcCmdline: gedit
ProcEnviron:
 PATH=(custom, user)
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f6f51107b57 <gd_tagged_entry_remove_tag+7>: mov 0x28(%rdi),%rax
 PC (0x7f6f51107b57) ok
 source "0x28(%rdi)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 gd_tagged_entry_remove_tag () from /usr/lib/x86_64-linux-gnu/gedit/libgedit.so
 ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit.so
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gedit crashed with SIGSEGV in gd_tagged_entry_remove_tag()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd mock plugdev sambashare sudo wireshark

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gd_tagged_entry_remove_tag (self=0x0, tag=0x0) at libgd/gd-tagged-entry.c:1084
 update_entry_tag (frame=0x58a8720) at gedit/gedit-view-frame.c:656
 update_entry_tag_idle_cb (frame=0x58a8720) at gedit/gedit-view-frame.c:686
 g_main_context_dispatch () from /tmp/apport_sandbox_s4igHq/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iterate.isra () from /tmp/apport_sandbox_s4igHq/lib/x86_64-linux-gnu/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gedit (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Eyeballed the attachments and cannot see anything sensitive in them. Making this public instead of private.

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.