GNOME Bugzilla – Bug 342550
Crash when left open for several hours
Last modified: 2007-01-14 18:52:32 UTC
Steps to reproduce: 1. Left Ekiga open (in another desktop), for several hours. 2. While in a different desktop got prompted to report ekiga crash. 3. Stack trace: From: <> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.14.0 Subject: Crashed when doing nothing Distribution: Ubuntu 6.06LTS (dapper) Package: ekiga Severity: Normal Version: GNOME2.14.1 unspecified Gnome-Distributor: Ubuntu Synopsis: Crashed when doing nothing Bugzilla-Product: ekiga Bugzilla-Component: ekiga Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? This is the first time. Additional Information: Using Ekiga version 2.0.1-20060521-01 Debugging Information: Backtrace was generated from '/usr/bin/ekiga-snapshot' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1244051776 (LWP 15233)] [New Thread -1293325392 (LWP 16599)] [New Thread -1291670608 (LWP 16598)] [New Thread -1291936848 (LWP 16597)] [New Thread -1296041040 (LWP 16596)] [New Thread -1294144592 (LWP 16219)] [New Thread -1294410832 (LWP 16218)] [New Thread -1293591632 (LWP 16210)] [New Thread -1294681168 (LWP 16209)] [New Thread -1290773584 (LWP 15631)] [New Thread -1290507344 (LWP 15630)] [New Thread -1282061392 (LWP 15499)] [New Thread -1257002064 (LWP 15491)] [New Thread -1245824080 (LWP 15361)] [New Thread -1245557840 (LWP 15360)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 68363
Thread 3 (Thread -1291670608 (LWP 16598))
Other information:
Thanks for the bug report! Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Installing ekiga-cvs-dbg would help having the symbols. Also, I would like to know if it crashed because it received a call, and how many accounts where registered. Basically, I'm wondering whether we have a clear bug or a vicious leak... if the crash is just over time, it's probably a leak. If there's a triggering event, a clear bug.
*** Bug 345616 has been marked as a duplicate of this bug. ***
I would like to have the debug symbols and to be sure that it also happens with 2.0.2. It crashes when receiving a PDU.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information Snark and Damien asked for. Thanks!
*** Bug 388336 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 367982 ***