indicator-weather crashed with SIGABRT in raise()

[Kim d'Audretsch]

Clicked on the weather applet icon and then the program crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 19 14:40:11 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, user)
 LANG=nl_NL.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: indicator-weather
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
Title: indicator-weather crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to oneiric on 2011-09-13 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7fa507bcf0d8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=3, str=0x7fa507bcf210 "double free or corruption (fasttop)", ptr=<optimized out>) at malloc.c:6283
 _int_realloc (av=0x7fa4ec000020, oldp=0x7fa4ec0009c0, oldsize=32, nb=<optimized out>) at malloc.c:5341
 __GI___libc_realloc (oldmem=0x7fa4ec0009d0, bytes=32) at malloc.c:3821
 g_realloc (mem=<optimized out>, n_bytes=32) at /build/buildd/glib2.0-2.29.92/./glib/gmem.c:242

[Launchpad Janitor (janitor)]

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

[dobey (dobey)]

Is anyone actually even looking at indicator-weather bugs? I literally have to manually restart the thing 5 times a day.

[Vadim Rutkovsky (roignac)]

This is reproducible for amd64 and releated to DBus menu, yet nobody has ever provided enough information - so could you please attach valgrind logs for this issue?

[dobey (dobey)]

Vadim, how exactly does one *force* the issue to happen? I am not on amd64. I don't think my bug is necessarily a dup of this one either, though apport retracer marked it as such. It is definitely a memory problem in the bug I filed though; bug #927676 . Perhaps it's the same issue simply resulting in different crashes on i386 and amd64 though.

Also nobody has stated exactly what "enough information" is here, or asked for anything specific beyond the valgrind log which you only now asked for. If you verified it is reproducible, then you have a way to reproduce it, and surely you can also attach some valgrind logs for the issue, no?

[Yrjö Pokkinen (ypokkinen-2)]

Here is valgrind of weather-indicator , so hope this helps. (Ubuntu 12.04 uname -r: 3.2.0-27-generic)

valgrind --leak-check=yes /usr/bin/indicator-weather

==15571== by 0x57D2D8: ??? (in /usr/bin/python2.7)
==15571== by 0x4EC79C: ??? (in /usr/bin/python2.7)
==15571== by 0x4E8DAA: ??? (in /usr/bin/python2.7)
==15571== by 0x4ECB0F: ??? (in /usr/bin/python2.7)
==15571== by 0x4ED157: ??? (in /usr/bin/python2.7)
==15571== by 0x4E8D9D: ??? (in /usr/bin/python2.7)
==15571== by 0x4ECB0F: ??? (in /usr/bin/python2.7)
==15571== by 0x498B8B: PyAST_Compile (in /usr/bin/python2.7)
==15571== by 0x42A0F6: PyRun_StringFlags (in /usr/bin/python2.7)
==15571== by 0x430BAE: PyEval_EvalFrameEx (in /usr/bin/python2.7)
==15571== by 0x4317F1: PyEval_EvalCodeEx (in /usr/bin/python2.7)
==15571==
==15571== Conditional jump or move depends on uninitialised value(s)
==15571== at 0x57A968: PyObject_Free (in /usr/bin/python2.7)
==15571== by 0x4EC79C: ??? (in /usr/bin/python2.7)
==15571== by 0x4E8DAA: ??? (in /usr/bin/python2.7)
==15571== by 0x4ECB0F: ??? (in /usr/bin/python2.7)
==15571== by 0x4ED157: ??? (in /usr/bin/python2.7)
==15571== by 0x4E8D9D: ??? (in /usr/bin/python2.7)
==15571== by 0x4ECB0F: ??? (in /usr/bin/python2.7)
==15571== by 0x498B8B: PyAST_Compile (in /usr/bin/python2.7)
==15571== by 0x42A0F6: PyRun_StringFlags (in /usr/bin/python2.7)
==15571== by 0x430BAE: PyEval_EvalFrameEx (in /usr/bin/python2.7)
==15571== by 0x4317F1: PyEval_EvalCodeEx (in /usr/bin/python2.7)
==15571== by 0x42A997: PyEval_EvalFrameEx (in /usr/bin/python2.7)
==15571==
==15571== Use of uninitialised value of size 8
==15571== at 0x57A980: PyObject_Free (in /usr/bin/python2.7)
==15571== by 0x4EC79C: ??? (in /usr/bin/python2.7)
==15571== by 0x4E8DAA: ??? (in /usr/bin/python2.7)
==15571== by 0x4ECB0F: ??? (in /usr/bin/python2.7)
==15571== by 0x4ED157: ??? (in /usr/bin/python2.7)
==15571== by 0x4E8D9D: ??? (in /usr/bin/python2.7)
==15571== by 0x4ECB0F: ??? (in /usr/bin/python2.7)
==15571== by 0x498B8B: PyAST_Compile (in /usr/bin/python2.7)
==15571== by 0x42A0F6: PyRun_StringFlags (in /usr/bin/python2.7)
==15571== by 0x430BAE: PyEval_EvalFrameEx (in /usr/bin/python2.7)
==15571== by 0x4317F1: PyEval_EvalCodeEx (in /usr/bin/python2.7)
==15571== by 0x42A997: PyEval_EvalFrameEx (in /usr/bin/python2.7)
==15571==
==15571== Invalid read of size 4
==15571== at 0x57A95F: PyObject_Free (in /usr/bin/python2.7)
==15571== by 0x444AB8: ??? (in /usr/bin/python2.7)
==15571== by 0x566B2C: ??? (in /usr/bin/python2.7)
==15571== by 0x4420A2: ??? (in /usr/bin/python2.7)
==15571== by 0x535901: ??? (in /usr/bin/python2.7)
==15571== by 0x42AC06: PyEval_EvalFrameEx (in /usr/bin/python2.7)
==15571== by 0x42ABE1: PyEval_EvalFrameEx (in /usr/bin/python2.7)
==15571== by 0x4317F1: PyEval_EvalCodeEx (in /usr/bin/python2.7)
==15571== by 0x42A997: PyEval_EvalFrameEx (in /usr/bin/python2.7)
==15571== by 0x4317F1: PyEval_EvalCodeEx (in /usr/bin/python2.7)
==15571== by 0x54AA3F: ??? (in /usr/bin/python2.7)
==15571== by 0x4C7C75: PyObject_Cal...

[Sasa Paporovic (melchiaros)]

In respect that this affects in sum 61 people I set the status of the upstream report to confirmed.

[Sasa Paporovic (melchiaros)]

I remove the question status of the report, because the question has the character of bug comment.

[Sasa Paporovic (melchiaros)]

Report

https://bugs.launchpad.net/ubuntu/+source/indicator-weather/+bug/741759

is identified as furhter dublicate, which shows that the first occurence of the crash can be followed back to Ubuntu11.04 natty with indicator-weather 11.03.20

This also raises the sum of affected people to 85.

[Olaf (hein-jessen)]

Ubuntu 13.04