Bug 343600 – s-j crashed when opening pref dialog

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 343600 - s-j crashed when opening pref dialog


Summary:	s-j crashed when opening pref dialog


Status:	RESOLVED FIXED

Product:	sound-juicer
Classification:	Applications
Component:	general
Version:	2.14.x
Hardware:	Other Linux

Importance:	Normal major
Target Milestone:	---
Assigned To:	Sound Juicer Maintainers
QA Contact:	Sound Juicer Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-06-01 14:36 UTC by Wouter Bolsterlee (uws)
Modified:	2006-06-18 17:04 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Wouter Bolsterlee (uws) 2006-06-01 14:36:48 UTC

s-j crashed when I quickly opened the prefs dialog twice (open, close, open again). I'm using 2.14.3

Backtrace was generated from '/opt/gnome/bin/sound-juicer'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1227831616 (LWP 5207)]
0xb7044221 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 68584

#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 792
#2 <signal handler called>
#3 IA__g_logv
#4 IA__g_log
at gmessages.c line 517
#5 IA__g_assert_warning
at gmessages.c line 552
#6 on_edit_preferences_cb
at sj-prefs.c line 347
#7 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#8 IA__g_closure_invoke
at gclosure.c line 490
#9 signal_emit_unlocked_R
at gsignal.c line 2438
#10 IA__g_signal_emit_valist
at gsignal.c line 2197
#11 IA__g_signal_emit
at gsignal.c line 2241
#12 IA__gtk_widget_activate
at gtkwidget.c line 3932
#13 IA__gtk_menu_shell_activate_item
at gtkmenushell.c line 1024
#14 gtk_menu_shell_button_release
at gtkmenushell.c line 630
#15 gtk_menu_button_release
at gtkmenu.c line 2619
#16 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 83
#17 g_type_class_meta_marshal
at gclosure.c line 567
#18 IA__g_closure_invoke
at gclosure.c line 490
#19 signal_emit_unlocked_R
at gsignal.c line 2476
#20 IA__g_signal_emit_valist
at gsignal.c line 2207
#21 IA__g_signal_emit
at gsignal.c line 2241
#22 gtk_widget_event_internal
at gtkwidget.c line 3901
#23 IA__gtk_propagate_event
at gtkmain.c line 2186
#24 IA__gtk_main_do_event
at gtkmain.c line 1420
#25 gdk_event_dispatch
at gdkevents-x11.c line 2314
#26 IA__g_main_context_dispatch
at gmain.c line 1916
#27 g_main_context_iterate
at gmain.c line 2547
#28 IA__g_main_loop_run
at gmain.c line 2751
#29 IA__gtk_main
at gtkmain.c line 999
#30 main
at sj-main.c line 1521

Comment 1 Elijah Newren 2006-06-01 16:33:43 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 316855 ***

Comment 2 Wouter Bolsterlee (uws) 2006-06-01 17:06:53 UTC

I'm not so sure this bug is really a dup of the one you mentioned. Bug #316855 has a crash in new_profile_response_callback, while this backtrace crashes in on_edit_preferences_cb, a quite different function... reopening.

Comment 3 Elijah Newren 2006-06-01 17:13:24 UTC

Indeed, definitely looks like a mistake on my part.  Sorry for the noise.

Comment 4 Wouter Bolsterlee (uws) 2006-06-01 17:17:01 UTC

Quote:

> First five function calls in the bug:
>
>   1. IA__g_assert_warning
>   2. on_edit_preferences_cb
>   3. IA__g_cclosure_marshal_VOID__VOID
>   4. IA__g_closure_invoke
>   5. signal_emit_unlocked_R

Highly irrelevant functions, Elijah. You should not trust the SIMPLE dup finder ;-P

Comment 5 Elijah Newren 2006-06-01 17:43:35 UTC

I know (having written a fair amount of the code for the simple-dup-finder); as always, I did try to look over the two bugs to compare, but must have either accidentally opened one of the bugs twice and thus compared the bug to itself (I do that every once in a long while) or made some other similarly dumb mistake.  Anyway, sorry for the noise.

Comment 6 Ross Burton 2006-06-18 17:04:50 UTC

Fixed in cvs, will be in 2.15.4 and 2.14.5.