nautilus crashed with SIGSEGV in tcache_get()

Bug #1788036 reported by Mohammad Hizzani
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

nautilus closed all of a sudden

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AssertionMessage: double free or corruption (fasttop)
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 20 23:26:18 2018
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'216'
 b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'"
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']"
ProcCmdline: /usr/bin/nautilus --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f7f019c1207 <__GI___libc_malloc+407>: mov (%rdx),%rdi
 PC (0x7f7f019c1207) ok
 source "(%rdx)" (0x6f73692e) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 tcache_get (tc_idx=0) at malloc.c:2943
 __GI___libc_malloc (bytes=17) at malloc.c:3050
 g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_strndup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_strsplit () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in tcache_get()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_nautilus:

Revision history for this message
Mohammad Hizzani (moh.hiz) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 tcache_get (tc_idx=0) at malloc.c:2943
 __GI___libc_malloc (bytes=bytes@entry=17) at malloc.c:3050
 g_malloc (n_bytes=n_bytes@entry=17) at ../../../../glib/gmem.c:99
 g_strndup (str=str@entry=0x55bdb0c3d798 "access::can-read,", n=n@entry=16) at ../../../../glib/gstrfuncs.c:425
 g_strsplit (string=string@entry=0x55bdb0c3d770 "standard::is-hidden,standard::is-backup,access::can-read,", delimiter=delimiter@entry=0x7f7f04357cab ",", max_tokens=2147483644, max_tokens@entry=-1) at ../../../../glib/gstrfuncs.c:2352

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 nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Martin Dauskardt (md001) wrote :

I also see the same segfault showing "tcache_get (tc_idx=0) at malloc.c:2943" when I use Thunar 1.8.1 on Xubuntu 18.04

Revision history for this message
esodan (esodan-gmail) wrote :

I'm developing libgda and found same issue when try to parse a connection string using g_strsplit():

#0 0x00007ffff6cd6207 in tcache_get (tc_idx=2) at malloc.c:2943
#1 0x00007ffff6cd6207 in __GI___libc_malloc (bytes=53) at malloc.c:3050
#2 0x00007ffff76748d9 in g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007ffff768e1bf in g_strdup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007ffff768f954 in g_strsplit () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007ffff7a0f05e in gda_quark_list_add_from_string (qlist=0x5555557c77a0, string=0x5555557e5640 "DB_NAME=test-463087209;DB_DIR=/home/despinosa/Proyectos/libgda/_build/tests", cleanup=0)
    at ../libgda/gda-quark-list.c:380

Also, hapends when tries to parse an XML configuration file:

#0 0x00007ffff6cd6207 in tcache_get (tc_idx=2) at malloc.c:2943
#1 0x00007ffff6cd6207 in __GI___libc_malloc (bytes=56) at malloc.c:3050
#2 0x00007ffff66ac686 in xmlNewCharEncodingHandler () at /usr/lib/x86_64-linux-gnu/libxml2.so.2
#3 0x00007ffff66ac48a in xmlInitCharEncodingHandlers () at /usr/lib/x86_64-linux-gnu/libxml2.so.2
#4 0x00007ffff66cdd25 in xmlParseFile () at /usr/lib/x86_64-linux-gnu/libxml2.so.2
#5 0x00007ffff79a1598 in load_config_file (file=0x55555578f9f0 "/home/despinosa/.local/share/libgda/config", is_system=0) at ../libgda/gda-config.c:561

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.