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 732796 - tracker-1.0.1: tracker-miner-fs segfault
tracker-1.0.1: tracker-miner-fs segfault
Status: RESOLVED DUPLICATE of bug 732615
Product: tracker
Classification: Core
Component: Miners
1.0.x
Other Linux
: Normal normal
: ---
Assigned To: tracker-general
Depends on:
Blocks:
 
 
Reported: 2014-07-06 10:57 UTC by Pacho Ramos
Modified: 2014-08-06 08:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Pacho Ramos 2014-07-06 10:57:15 UTC 
Program terminated with signal 11, Segmentation fault.

+ Trace 233779

Thread 1 (Thread 0x7fa34bdb9700 (LWP 10023))

  • #0 magazine_chain_pop_head
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gslice.c line 539
  • #1 thread_memory_magazine1_alloc
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gslice.c line 842
  • #2 g_slice_alloc
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gslice.c line 998
  • #3 g_slice_alloc0
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gslice.c line 1032
  • #4 g_source_new
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c line 864
  • #5 g_timeout_source_new
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c line 4498
  • #6 ik_read_callback
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/gio/inotify/inotify-kernel.c line 368
  • #7 g_main_dispatch
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c line 3064
  • #8 g_main_context_dispatch
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c line 3663
  • #9 g_main_context_iterate
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c line 3734
  • #10 g_main_context_iteration
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c line 3795
  • #11 glib_worker_main
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c line 5541
  • #12 g_thread_proxy
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gthread.c line 764
  • #13 start_thread
    at pthread_create.c line 308
  • #14 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 113 






Comment 1


Martyn Russell





          2014-07-07 10:35:16 UTC
        



Hi there, are you able to reliably reproduce this?






Comment 2


Pacho Ramos





          2014-07-07 12:29:58 UTC
        



not for now :/






Comment 3


Martyn Russell





          2014-07-07 13:51:24 UTC
        



I have a strong suspicion this is related to a bug Martin Kampas has reported so I am marking as duplicate for now. If you have reason to believe otherwise, please reopen. Thanks Pacho.

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






Comment 4


Philip Van Hoof





          2014-08-02 13:22:44 UTC
        



Hi Martyn, on what is your suspicion based? That could be interesting for investigation.






Comment 5


Martyn Russell





          2014-08-06 08:05:44 UTC
        



(In reply to comment #4)
> Hi Martyn, on what is your suspicion based? That could be interesting for
> investigation.

Well, I have no real information to go on actually. But the only crash we're seeing right now (not related to extracting metadata) is in the tracker-store and that's because of this DBus error message limitation causing a g_error()/abort.

As said, I don't actually have any useful information in the backtrace sadly and I have not seen anyway to reproduce this. So that's the only likely candidate right now.