Bug 349872 – crash on Gossip Instant Messenger when exiting program

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 349872 - crash on Gossip Instant Messenger when exiting program


Summary:	crash on Gossip Instant Messenger when exiting program


Status:	RESOLVED FIXED

Product:	gossip
Classification:	Deprecated
Component:	General
Version:	0.14
Hardware:	Other Linux

Importance:	High normal
Target Milestone:	---
Assigned To:	Gossip Maintainers
QA Contact:	Gossip Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-08-04 01:54 UTC by Jose M. daLuz
Modified:	2006-08-06 19:10 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Jose M. daLuz 2006-08-04 01:54:03 UTC

What were you doing when the application crashed?
Exiting the application


Distribution: Gentoo Base System version 1.12.4
Gnome Release: 2.15.90 2006-07-25 (Gentoo)
BugBuddy Version: 2.15.90

Memory status: size: 198115328 vsize: 198115328 resident: 18182144 share: 12820480 rss: 18182144 rss_rlim: -1
CPU usage: start_time: 1154656087 rtime: 140 utime: 129 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gossip'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46915935765456 (LWP 23405)]
0x00002aab75d7d8f5 in __libc_waitpid (pid=23516, stat_loc=0x7fff397435bc, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 69952

Thread 1 (Thread 46915935765456 (LWP 23405))

#0 __libc_waitpid
at ../sysdeps/unix/sysv/linux/waitpid.c line 32
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 867
#2 <signal handler called>
#3 IA__g_logv
at gmessages.c line 493
#4 IA__g_log
at gmessages.c line 517
#5 g_hash_nodes_destroy
at ghash.c line 783
#6 IA__g_hash_table_remove_all
at ghash.c line 468
#7 IA__g_hash_table_destroy
at ghash.c line 221
#8 app_finalize
at gossip-app.c line 378
#9 IA__g_object_unref
at gobject.c line 1762
#10 main
at gossip-main.c line 207

Comment 1 Jose M. daLuz 2006-08-04 01:57:05 UTC

I had just installed Gossip, setup my Google Talk account, but was unsuccessful in connecting. I clicked on the close button and this crash happened.

Comment 2 Richard Hult 2006-08-04 09:26:26 UTC

Will look at this tonight. Crashing on exit is hardly critical, it just makes the app quit faster! ;)

Your stacktrace looks a bit corrupt, could you try running it directly in gdb instead to get a better one?

Comment 3 Richard Hult 2006-08-04 09:30:14 UTC

Ah, the track does look right after all, nevermind.

Comment 4 Jose M. daLuz 2006-08-04 12:35:58 UTC

(In reply to comment #2)
> Crashing on exit is hardly critical, it just makes
> the app quit faster! ;)
All of the critical warnings cause bug-buddy to make the bug critical, no matter how trivial the cause. I usually leave it to the developer to make the judgment call, as you did. ;-)

Comment 5 Richard Hult 2006-08-06 19:10:27 UTC

Ah, didn't know that bug-buddy did that, thanks :)

I've worked around the bug in CVS, by not freeing the errors hash table on exit, that's good enough since doing it the right way would too much work for no gain (it's not a leak, freeing was only done to help finding other leaks on exit).