Bug 664836 – gedit crashed with SIGSEGV in g_slice_alloc() when opening file with zeros

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 664836 - gedit crashed with SIGSEGV in g_slice_alloc() when opening file with zeros


Summary:	gedit crashed with SIGSEGV in g_slice_alloc() when opening file with zeros


Status:	RESOLVED INCOMPLETE

Product:	gedit
Classification:	Applications
Component:	general
Version:	3.2.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	Gedit maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-11-25 18:59 UTC by Pedro Villavicencio
Modified:	2012-01-13 06:03 UTC

See Also:
GNOME target:	---
GNOME version:	3.1/3.2

Description Pedro Villavicencio 2011-11-25 18:59:53 UTC

this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/885330

"Gedit crashes if it tries to open file that contains zero bytes (like file example.txt in attachment)."

https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/885330/+attachment/2583266/+files/example.txt

valgrind logs: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/885330/+attachment/2601554/+files/valgrind.log.gz

".

+ Trace 229135

Thread 1 (Thread 0xb76e4870 (LWP 22750))

#0 magazine_chain_pop_head
at /build/buildd/glib2.0-2.30.0/./glib/gslice.c line 492
#1 thread_memory_magazine1_alloc
at /build/buildd/glib2.0-2.30.0/./glib/gslice.c line 795
#2 g_slice_alloc
at /build/buildd/glib2.0-2.30.0/./glib/gslice.c line 833
#3 g_string_sized_new
at /build/buildd/glib2.0-2.30.0/./glib/gstring.c line 420
#4 g_markup_escape_text
at /build/buildd/glib2.0-2.30.0/./glib/gmarkup.c line 2182
#5 bookmark_app_info_dump
at /build/buildd/glib2.0-2.30.0/./glib/gbookmarkfile.c line 303
#6 bookmark_metadata_dump
at /build/buildd/glib2.0-2.30.0/./glib/gbookmarkfile.c line 465
#7 bookmark_item_dump
at /build/buildd/glib2.0-2.30.0/./glib/gbookmarkfile.c line 634
#8 g_bookmark_file_dump
at /build/buildd/glib2.0-2.30.0/./glib/gbookmarkfile.c line 1561
#9 g_bookmark_file_to_data
at /build/buildd/glib2.0-2.30.0/./glib/gbookmarkfile.c line 1948
#10 g_bookmark_file_to_file
at /build/buildd/glib2.0-2.30.0/./glib/gbookmarkfile.c line 1986
#11 gtk_recent_manager_real_changed
at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkrecentmanager.c line 481
#12 g_cclosure_marshal_VOID__VOID
at /build/buildd/glib2.0-2.30.0/./gobject/gmarshal.c line 85
#13 g_type_class_meta_marshal
at /build/buildd/glib2.0-2.30.0/./gobject/gclosure.c line 885
#14 g_closure_invoke
at /build/buildd/glib2.0-2.30.0/./gobject/gclosure.c line 774
#15 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c line 3202
#16 g_signal_emit_valist
at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c line 3003
#17 g_signal_emit
at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c line 3060
#18 emit_manager_changed
at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkrecentmanager.c line 1358
#19 gdk_threads_dispatch
at /build/buildd/gtk+3.0-3.2.0/./gdk/gdk.c line 754
#20 g_timeout_dispatch
at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3907
#21 g_main_dispatch
at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 2441
#22 g_main_context_dispatch
at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3011
#23 g_main_context_iterate
at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3089
#24 g_main_loop_run
at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3297
#25 gtk_main
at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkmain.c line 1367
#26 gedit_main
at gedit.c line 199
#27 main
at gedit.c line 290

Comment 1 Paolo Borelli 2011-11-26 15:51:32 UTC

I cannot reproduce with current master. I think it was a bug in gtk or in ubuntu specific patches... Can you reproduce with gtk and gedit built from git master?

Comment 2 Akhil Laddha 2012-01-13 06:03:51 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!