python2.7 crashed with SIGSEGV in _int_malloc()

Bug #1296254 reported by Jaime Pérez
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
playonlinux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Appears when trying to make a new prefix in playonlinux

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: python2.7-minimal 2.7.6-8
ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6
Uname: Linux 3.13.0-19-lowlatency x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Sun Mar 23 12:20:33 2014
ExecutablePath: /usr/bin/python2.7
InstallationDate: Installed on 2014-02-08 (42 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: python mainwindow.py
SegvAnalysis:
 Segfault happened at: 0x7fb9dffe0bc1 <_int_malloc+689>: mov %r14,0x10(%r9)
 PC (0x7fb9dffe0bc1) ok
 source "%r14" ok
 destination "0x10(%r9)" (0x1c0000001810) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
 _int_malloc (av=av@entry=0x7fb9e031f760 <main_arena>, bytes=bytes@entry=200) at malloc.c:3489
 __libc_calloc (n=<optimized out>, elem_size=<optimized out>) at malloc.c:3219
 hb_font_create () from /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0
 pango_shape_full () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
Title: python2.7 crashed with SIGSEGV in _int_malloc()
UpgradeStatus: Upgraded to trusty on 2014-03-07 (15 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Jaime Pérez (jaime-91) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1290971, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
Revision history for this message
Jaime Pérez (jaime-91) wrote :

Looking for python... 2.7.6 - selected
[main] Message: PlayOnLinux (4.2.2) is starting
[clean_tmp] Message: Cleaning temp directory
[POL_System_CheckFS] Message: Checking filesystem for /home/jaime/.PlayOnLinux/
[main] Message: Filesystem is compatible
ATENCIÓN: Por favor, use en primer lugar POL_SetupWindow_Init
[install_plugins] Message: Checking plugin: ScreenCap...
[install_plugins] Message: Checking plugin: PlayOnLinux Vault...
[maj_check] Message: List is up to date
[POL_SetupWindow_Init] Message: Creating new window for pid 27683
[POL_SetupWindow_menu_num] Message: menu_num answer: 1
[POL_System_SetArch] Message: POL_ARCH set to amd64
*** Error in `python': malloc(): memory corruption: 0x0000000002dd2260 ***
/usr/share/playonlinux/playonlinux: line 115: 27067 Segmentation fault (core dumped) "$POL_PYTHON" mainwindow.py "$@"

Matthias Klose (doko)
affects: python2.7 (Ubuntu) → playonlinux (Ubuntu)
information type: Private → Public
Revision history for this message
Ronin Dusette (ronindusette) wrote :

Update your POL version to 4.2.4 from playonlinux.com and see if that helps. This should not be an issue at all. Your debug output looks weird, like it was cut up/edited. Do you have the raw output? If not, we can close this ticket tomorrow, as this seems to be a lone issue, and not a bug to POL itself.

Revision history for this message
Ronin Dusette (ronindusette) wrote :

No response, and this is an isolated report. Closing.

Changed in playonlinux (Ubuntu):
status: New → Invalid
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.