Bug 618455 – Crash (freeing invalid pointer) when deleting bookmarks

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 618455 - Crash (freeing invalid pointer) when deleting bookmarks


Summary:	Crash (freeing invalid pointer) when deleting bookmarks


Status:	RESOLVED OBSOLETE

Product:	bluefish
Classification:	Other
Component:	application
Version:	2.0.0
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Bluefish Maintainer(s)
QA Contact:	Bluefish Maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-05-12 14:46 UTC by Paul Howarth
Modified:	2011-08-31 10:03 UTC

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

Attachments
Backtrace from crash (22.53 KB, text/plain) 2010-05-12 14:46 UTC, Paul Howarth	Details

Description Paul Howarth 2010-05-12 14:46:07 UTC

Created attachment 160904 [details]
Backtrace from crash

This crash, observed when deleting bookmarks, was originally reported at https://bugzilla.redhat.com/show_bug.cgi?id=590257

There's a "free(): invalid pointer" in Thread 1 of the backtrace.

Comment 1 Fabio Durán Verdugo 2010-05-12 16:58:47 UTC

Paste here the trace
[New Thread 14106]
Core was generated by `bluefish /home/leo/docs/kn/kn.bfproject'.
Program terminated with signal 6, Aborted.

+ Trace 221876

Thread 1 (Thread 14104)

#0 raise
at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
#1 abort
at abort.c line 92
#2 __libc_message
at ../sysdeps/unix/sysv/linux/libc_fatal.c line 186
#3 malloc_printerr
#4 IA__g_strfreev
at gstrfuncs.c line 2558
#5 bmark_unstore
at bookmark.c line 415
#6 bmark_del_children_backend
at bookmark.c line 575
#7 bmark_del_all
at bookmark.c line 1656
#8 bmark_rpopup_action_lcb
at bookmark.c line 673
#9 IA__g_closure_invoke
at gclosure.c line 767
#10 signal_emit_unlocked_R
at gsignal.c line 3248
#11 IA__g_signal_emit_valist
at gsignal.c line 2981
#12 IA__g_signal_emit
at gsignal.c line 3038
#13 IA__gtk_widget_activate
at gtkwidget.c line 4989
#14 IA__gtk_menu_shell_activate_item
at gtkmenushell.c line 1283
#15 gtk_menu_shell_button_release
at gtkmenushell.c line 710
#16 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#17 IA__g_closure_invoke
at gclosure.c line 767
#18 signal_emit_unlocked_R
at gsignal.c line 3286
#19 IA__g_signal_emit_valist
at gsignal.c line 2991
#20 IA__g_signal_emit
at gsignal.c line 3038
#21 gtk_widget_event_internal
at gtkwidget.c line 4958
#22 IA__gtk_propagate_event
at gtkmain.c line 2442
#23 IA__gtk_main_do_event
at gtkmain.c line 1647
#24 gdk_event_dispatch
at gdkevents-x11.c line 2372
#25 g_main_dispatch
at gmain.c line 1960
#26 IA__g_main_context_dispatch
at gmain.c line 2513
#27 g_main_context_iterate
at gmain.c line 2591
#28 IA__g_main_loop_run
at gmain.c line 2799
#29 IA__gtk_main
at gtkmain.c line 1219
#30 main
at bluefish.c line 332

Comment 2 Olivier Sessink 2010-05-16 12:30:06 UTC

I cannot reproduce it on Fedora 12 64bit with the 64bit rpm that we provide ourselves bluefish-2.0.0.5.fc12.x86_64.rpm  

can you give the official rpm a try?

Comment 3 Paul Howarth 2010-05-18 14:42:58 UTC

The original reporter is using a Fedora 13 test release (Fedora 13 final is imminent); is there an official Fedora 13 build or should I try to get them to use the Fedora 12 build?

Does the 2.0.0.5 build contain patches on top of the 2.0.0 release? If so, where can I find the spec and patches - I can update the Fedora 13 package to include the same patches if necessary.

Comment 4 Tobias Mueller 2010-10-09 00:55:20 UTC

Olivier, can you address the questions raised in comment #3?

Comment 5 Jim Hayward 2010-10-09 01:08:22 UTC

I've never been able to reproduce this issue on F13. It may have been fixed along with other changes. It's possible it takes a very specific sequence of actions and/or settings to trigger it that I have not reproduced. There is nothing obvious in the code that might have caused the crash.