python2.7 crashed with SIGSEGV in _int_malloc()

Bug #1725713 reported by otheos
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gtk+3.0 (Ubuntu)
New
Medium
Unassigned

Bug Description

ubuntu-after-install crashed.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: python2.7-minimal 2.7.14-2ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sat Oct 21 15:38:11 2017
ExecutablePath: /usr/bin/python2.7
InstallationDate: Installed on 2017-10-19 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: python ubuntu-after-install.py
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
 TERM=unknown
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7fccac45f310 <_int_malloc+1536>: mov 0x10(%rdx),%rsi
 PC (0x7fccac45f310) ok
 source "0x10(%rdx)" (0x56010000001b) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
 _int_malloc (av=av@entry=0x7fccac7adc20 <main_arena>, bytes=bytes@entry=12) at malloc.c:3611
 __libc_calloc (n=<optimised out>, elem_size=<optimised out>) at malloc.c:3438
 g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gtk_tree_path_to_string () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: python2.7 crashed with SIGSEGV in _int_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
otheos (ubuntu-otheos) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _int_malloc (av=av@entry=0x7fccac7adc20 <main_arena>, bytes=bytes@entry=12) at malloc.c:3611
 __libc_calloc (n=n@entry=1, elem_size=elem_size@entry=12) at malloc.c:3438
 g_malloc0 (n_bytes=n_bytes@entry=12) at ../../../../glib/gmem.c:124
 gtk_tree_path_to_string (path=path@entry=0x5601a25ad8a0) at ././gtk/gtktreemodel.c:743
 gtk_cell_area_real_apply_attributes (area=<optimized out>, tree_model=<optimized out>, iter=0x5601a23b7920, is_expander=<optimized out>, is_expanded=<optimized out>) at ././gtk/gtkcellarea.c:1291

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 python2.7 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Matthias Klose (doko) wrote :

more likely an isssue in gtk+3.0 or it's python bindings

affects: python2.7 (Ubuntu) → gtk+3.0 (Ubuntu)
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.