Bug 707259 – tracker-miner-fs crashed with SIGSEGV in magazine_chain_pop_head()

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 707259 - tracker-miner-fs crashed with SIGSEGV in magazine_chain_pop_head()


Summary:	tracker-miner-fs crashed with SIGSEGV in magazine_chain_pop_head()


Status:	RESOLVED INCOMPLETE

Product:	tracker
Classification:	Core
Component:	Miners
Version:	0.16.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	tracker-general
QA Contact:

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2013-09-02 03:37 UTC by Cristian Aravena Romero
Modified:	2014-01-09 14:06 UTC

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

Description Cristian Aravena Romero 2013-09-02 03:37:53 UTC

Open bug in launchpad.net

https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1219606

"I'm working with Ubuntu and Crash."

+ Trace 232443

#0 magazine_chain_pop_head
at /build/buildd/glib2.0-2.37.6/./glib/gslice.c line 545
#1 thread_memory_magazine1_alloc
at /build/buildd/glib2.0-2.37.6/./glib/gslice.c line 848
#2 g_slice_alloc
at /build/buildd/glib2.0-2.37.6/./glib/gslice.c line 1007
#3 g_slice_alloc0
at /build/buildd/glib2.0-2.37.6/./glib/gslice.c line 1042
#4 g_type_create_instance
at /build/buildd/glib2.0-2.37.6/./gobject/gtype.c line 1850
#5 g_object_new_internal
at /build/buildd/glib2.0-2.37.6/./gobject/gobject.c line 1746
#6 g_object_newv
at /build/buildd/glib2.0-2.37.6/./gobject/gobject.c line 1890
#7 g_object_new
at /build/buildd/glib2.0-2.37.6/./gobject/gobject.c line 1556
#8 _g_local_file_new
at /build/buildd/glib2.0-2.37.6/./gio/glocalfile.c line 300
#9 g_daemon_vfs_get_file_for_path
at gdaemonvfs.c line 394
#10 ih_event_callback
at /build/buildd/glib2.0-2.37.6/./gio/inotify/inotify-helper.c line 181
#11 ip_event_dispatch
at /build/buildd/glib2.0-2.37.6/./gio/inotify/inotify-path.c line 493
#12 ip_event_callback
at /build/buildd/glib2.0-2.37.6/./gio/inotify/inotify-path.c line 629
#13 ik_process_eq_callback
at /build/buildd/glib2.0-2.37.6/./gio/inotify/inotify-kernel.c line 579
#14 g_timeout_dispatch
at /build/buildd/glib2.0-2.37.6/./glib/gmain.c line 4450
#15 g_main_dispatch
at /build/buildd/glib2.0-2.37.6/./glib/gmain.c line 3065
#16 g_main_context_dispatch
at /build/buildd/glib2.0-2.37.6/./glib/gmain.c line 3641
#17 g_main_context_iterate
at /build/buildd/glib2.0-2.37.6/./glib/gmain.c line 3712
#18 g_main_context_iteration
at /build/buildd/glib2.0-2.37.6/./glib/gmain.c line 3773
#19 glib_worker_main
at /build/buildd/glib2.0-2.37.6/./glib/gmain.c line 5472
#20 g_thread_proxy
at /build/buildd/glib2.0-2.37.6/./glib/gthread.c line 798
#21 start_thread
at pthread_create.c line 311
#22 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 113

Comment 1 Martyn Russell 2013-09-30 10:31:03 UTC

What version of 0.16 are you using?

Comment 2 Tobias Mueller 2014-01-09 14:06:25 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!