GNOME Bugzilla – Bug 689905
tracker-miner-fs crashed with SIGSEGV in type_get_qdata_L()
Last modified: 2021-05-26 22:26:19 UTC
The report on this tracker 0.14.4 crasher was original filed to launchpad and has occured on Ubuntu13.04 Raring 64bit, which can be downloaded for reproducing purposes from http://cdimage.ubuntu.com/daily-live/current/ A stacktrace is available and will be copied here. The affected .zip could not be attached, because of the size(arround 500MB). A Download URL will be provided. The header of the launchpad report will be copied here. -----------------------(launchpad report header): tracker crashed after extracting a archive. Steps to reproduce: 1.Download http://sourceforge.net/projects/talend-studio/files/latest/download Talend Open Studio 2.Extract the .zip with nautilus -> right mouse click on .zip -> Extract here in /home/user/Downloads 3.See tracker crashing after the extraction has completed(takes a minute). ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: tracker-miner-fs 0.14.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-5.13-generic 3.7.0-rc8 Uname: Linux 3.7.0-5-generic x86_64 ApportVersion: 2.6.3-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Sat Dec 8 19:35:23 2012 ExecutablePath: /usr/lib/tracker/tracker-miner-fs InstallationDate: Installed on 2012-07-22 (139 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120722) MarkForUpload: True ProcCmdline: /usr/lib/tracker/tracker-miner-fs ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR=<set> LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fb7de85a27c <g_type_check_is_value_type+316>: mov (%rax),%ecx PC (0x7fb7de85a27c) ok source "(%rax)" (0x00000100) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: g_type_check_is_value_type () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_value_type_compatible () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: tracker-miner-fs crashed with SIGSEGV in g_type_check_is_value_type() UpgradeStatus: Upgraded to raring on 2012-11-15 (22 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
+ Trace 231268
+ Trace 231269
.
+ Trace 231270
Thread 1 (Thread 0x7fb7dfcf7840 (LWP 2811))
The traces are 1:Stacktrace 2:StacktraceSource 3:StackstraceThread
Hello melchiaros, are you able to submit logs to show what is going on here? This might track down the issue more easily. I suspect the extractor might be dying. The stack traces above aren't really too useful sadly. For details on how to get logs for debugging, see: https://live.gnome.org/Tracker/Documentation/Debugging Thanks!
Following your guide I have set tracker-control --set-log-verbosity debug Than I have reproduced the crash(which is still there). I now attach the 3 logs from /home/user/.local/share/tracker
Unfortunally all 3 logs are larger than 1MB, which makes bugzilla rejecting them. I compress with .tar.bz2 and attach.
Created attachment 231630 [details] tracker logs in tar.bz2 format
In tracker-miner-fs.log the crash start arround: 15 Dez 2012, 18:35:00: GLib-GIO-Critical **: Error while sending AddMatch() message: Verbindung ist geschlossen 15 Dez 2012, 18:39:32: GLib-GIO-Critical **: g_file_get_child: assertion `G_IS_FILE (file)' failed 15 Dez 2012, 18:39:32: GLib-GObject-Critical **: g_object_set_qdata_full: assertion `G_IS_OBJECT (object)' failed 15 Dez 2012, 18:39:32: GLib-GObject-Critical **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
Hello Martyn, I have hit this again with tracker0.14.5 in Ubuntu13.04 final 64 bit on usage pbuilder to backport concavity package from Ubuntu13.04 -> Ubuntu12.10 -> Ubuntu12.04. The complete procedure I have used is complicated, so I destill no reproducing procedure from it. I just whant to notify you that the crasher is still there and can be hit by different ways. greetings melchiaros
(In reply to comment #10) > Hello Martyn, Hello, > I have hit this again with tracker0.14.5 in Ubuntu13.04 final 64 bit on usage > > pbuilder to backport concavity package from Ubuntu13.04 -> Ubuntu12.10 -> > Ubuntu12.04. > > The complete procedure I have used is complicated, so I destill no reproducing > procedure from it. > > I just whant to notify you that the crasher is still there and can be hit by > different ways. If you can tell me how to reproduce this, it would be useful. Thanks,
I have already done this in the description of the report: Steps to reproduce: 1.Download http://sourceforge.net/projects/talend-studio/files/latest/download Talend Open Studio 2.Extract the .zip with nautilus -> right mouse click on .zip -> Extract here in /home/user/Downloads 3.See tracker crashing after the extraction has completed(takes a minute). ------------------ My last comment was only there to point on that there are other ways to hit this crasher, even when I have no easy reproducing procedure for this other way over pbuilder/backporting.
(In reply to comment #12) > I have already done this in the description of the report: > > Steps to reproduce: > > 1.Download > > http://sourceforge.net/projects/talend-studio/files/latest/download > > Talend Open Studio > > 2.Extract the .zip with nautilus -> right mouse click on .zip -> Extract here > in /home/user/Downloads > > 3.See tracker crashing after the extraction has completed(takes a minute). > > ------------------ > > My last comment was only there to point on that there are other ways to hit > this crasher, even when I have no easy reproducing procedure for this other way > over pbuilder/backporting. Interesting, we have a similar bug which is showing the same symptoms here: https://bugzilla.gnome.org/show_bug.cgi?id=689410
Yes, I knoe it in meantime. I have filed both and get automatically notificaitons. I have not merged them, becuase the crash lines(see summary) are not the same.
This issue is observed again for Ubuntu13.10 saucy development branch with tracker0.16.1. This observation was done by a other user on the downstream report. Reproducing procedure is already given here, as requested.Logs also.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/tracker/-/issues/ Thank you for your understanding and your help.