gedit crashed with SIGSEGV in gtk_list_store_clear()

[knight]

gedit crashed with SIGSEGV in gtk_list_store_clear()

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gedit 3.18.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Apr 11 22:35:26 2016
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2016-03-15 (27 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: gedit /home/username/ZaloSetupLinux.deb
SegvAnalysis:
 Segfault happened at: 0x7f7de39ad8fe <gtk_list_store_clear+46>: cmp (%rdx),%rax
 PC (0x7f7de39ad8fe) ok
 source "(%rdx)" (0x00001000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 gtk_list_store_clear () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 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
Title: gedit crashed with SIGSEGV in gtk_list_store_clear()
UpgradeStatus: Upgraded to xenial on 2016-04-06 (5 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Jiannan (jiannan-redhat-bugs)]

Description of problem:
Gedit hangs periodically 2-3 minutes and sometime was forced quit. Just open a file and type. BTW, my system was updated from Fedora 21 using fedup. Didn't see this issue in Fedora 21.

Version-Release number of selected component:
gedit-3.16.2-1.fc22

Additional info:
reporter: libreport-2.5.1
backtrace_rating: 4
cmdline: /usr/bin/gedit --gapplication-service
crash_function: g_type_check_instance_is_a
executable: /usr/bin/gedit
global_pid: 4144
kernel: 4.0.4-303.fc22.x86_64
runlevel: N 5
type: CCpp
uid: 1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 g_type_check_instance_is_a at gtype.c:4016
 #1 gtk_list_store_clear at gtkliststore.c:1423
 #2 real_populate_liststore at gedit/gedit-open-document-selector.c:488
 #7 g_main_context_iteration at gmain.c:3869
 #8 g_application_run at gapplication.c:2308

[Jiannan (jiannan-redhat-bugs)]

Created attachment 1040253
File: backtrace

[Jiannan (jiannan-redhat-bugs)]

Created attachment 1040254
File: cgroup

[Jiannan (jiannan-redhat-bugs)]

Created attachment 1040255
File: core_backtrace

[Jiannan (jiannan-redhat-bugs)]

Created attachment 1040256
File: dso_list

[Jiannan (jiannan-redhat-bugs)]

Created attachment 1040257
File: environ

[Jiannan (jiannan-redhat-bugs)]

Created attachment 1040258
File: limits

[Jiannan (jiannan-redhat-bugs)]

Created attachment 1040259
File: maps

[Jiannan (jiannan-redhat-bugs)]

Created attachment 1040260
File: mountinfo

[Jiannan (jiannan-redhat-bugs)]

Created attachment 1040261
File: namespaces

[Jiannan (jiannan-redhat-bugs)]

Created attachment 1040262
File: open_fds

[Jiannan (jiannan-redhat-bugs)]

Created attachment 1040263
File: proc_pid_status

[Jiannan (jiannan-redhat-bugs)]

Created attachment 1040264
File: var_log_messages

[Apport retracing service (apport)]

StacktraceTop:
 gtk_list_store_clear (list_store=0x156b570) at /build/gtk+3.0-lL7YRg/gtk+3.0-3.18.9/./gtk/gtkliststore.c:1423
 real_populate_liststore (data=0x14cc340) at gedit/gedit-open-document-selector.c:518
 gdk_threads_dispatch (data=0xf30840) at /build/gtk+3.0-lL7YRg/gtk+3.0-3.18.9/./gdk/gdk.c:719
 g_main_context_dispatch () from /tmp/apport_sandbox_rGEU1J/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iterate.isra () from /tmp/apport_sandbox_rGEU1J/lib/x86_64-linux-gnu/libglib-2.0.so.0

[Launchpad Janitor (janitor)]

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

[Fedora (fedora-redhat-bugs)]

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.