ekiga crashed with SIGSEGV in calloc()

Bug #352215 reported by Zer0wL
50
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ekiga
Expired
Medium
ekiga (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: ekiga

lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

apt-cache policy ekiga
ekiga:
  Установлен: 3.2.0-0ubuntu1
  Кандидат: 3.2.0-0ubuntu1
  Таблица версий:
 *** 3.2.0-0ubuntu1 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

Just upgraded to 3.2.0 from 3.0.1 and when exiting ekiga it crashed....
Before it was functional very well

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/ekiga
Package: ekiga 3.2.0-0ubuntu1
ProcCmdline: ekiga
ProcEnviron:
 PATH=(custom, user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: ekiga
StacktraceTop:
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 calloc () from /lib/libc.so.6
 IA__g_malloc0 (n_bytes=2032)
 IA__g_slice_alloc (mem_size=24)
Title: ekiga crashed with SIGSEGV in calloc()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin mysql netdev plugdev powerdev pulse pulse-access scanner sudo vboxusers video

Revision history for this message
Zer0wL (zeroowl) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:malloc_consolidate (av=0x7f6ad2f61a00) at malloc.c:4889
_int_malloc (av=0x7f6ad2f61a00, bytes=2032)
__libc_calloc (n=<value optimized out>,
IA__g_malloc0 (n_bytes=2032)
IA__g_slice_alloc (mem_size=24)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
visibility: private → public
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in ekiga (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Zer0wL (zeroowl) wrote :

As you asked, this is a valgrind log after the crash happend again.
It need to work for few hours to reproduce this crash

Revision history for this message
Felix Geyer (debfx) wrote :

I can confirm this. ekiga sometimes crashes when I quit it.

Changed in ekiga (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Yannick Defais (sevmek) wrote :

Hi,

Ekiga 3.2.6 was released yesterday. It fix numerous issues. Could you please give it a try to check if it solves your issue?

https://launchpad.net/~sevmek/+archive/ekiga-released
(instructions and packages)

Best regards,
Yannick

Revision history for this message
Monkey (monkey-libre) wrote :

I´ve made an upstream for the Ekiga developers. Thank You for making Ubuntu better.

Changed in ekiga:
importance: Undecided → Unknown
status: New → Unknown
Revision history for this message
Vish (vish) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
 You reported this bug a while ago with ekiga version 3.2.0-0ubuntu1.

We were wondering if this is still an issue for you with the latest version .
[If you are using The Karmic Koala = version 3.2.5-1ubuntu1
Or in The Jaunty Jackalope = version 3.2.0-0ubuntu2 ]

Can you try with the latest ekiga version and report back ? Thanks in advance.

Changed in ekiga (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Alexey Kotlyarov (koterpillar) wrote :

This does not happen for me anymore with Karmic's ekiga.

Revision history for this message
Vish (vish) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update.
For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status.
Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[If anyone is still seeing the crash in jaunty , kindly report back]

Changed in ekiga (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Vish (vish) wrote :

Upstream comments also recommend upgrading to latest ekiga version.

Changed in ekiga:
importance: Unknown → Medium
status: Unknown → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.