tracker-miner-fs-3 crashed with SIGSEGV in finish_current_directory()

Bug #1959466 reported by Erich Eickmeyer
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
tracker-miners (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

System started running hot, and then the apport dialog appeared with a crashed tracker. I can only assume the system was in the process of indexing and ran into something it struggled to index.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: tracker-miner-fs 3.1.3-1
ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12
Uname: Linux 5.15.0-18-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Jan 28 16:30:28 2022
ExecutablePath: /usr/libexec/tracker-miner-fs-3
ExecutableTimestamp: 1632070789
InstallationDate: Installed on 2021-08-19 (162 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818)
ProcCmdline: /usr/libexec/tracker-miner-fs-3
ProcCwd: /home/erich
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f834c5e62a8: mov 0x28(%rax),%edx
 PC (0x7f834c5e62a8) ok
 source "0x28(%rax)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tracker-miners
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/tracker-miners-3.0/libtracker-miner-3.0.so
 ?? () from /usr/lib/x86_64-linux-gnu/tracker-miners-3.0/libtracker-miner-3.0.so
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: tracker-miner-fs-3 crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 finish_current_directory (notifier=0x564d17818ce0, interrupted=1) at ../src/libtracker-miner/tracker-file-notifier.c:603
 crawler_get_cb (crawler=<optimized out>, result=<optimized out>, user_data=user_data@entry=0x564d17818ce0) at ../src/libtracker-miner/tracker-file-notifier.c:505
 g_task_return_now (task=0x7f8320003b40) at ../../../gio/gtask.c:1223
 complete_in_idle_cb (task=0x7f8320003b40) at ../../../gio/gtask.c:1237
 g_main_dispatch (context=0x564d177f8a70) at ../../../glib/gmain.c:3413

tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in tracker-miners (Ubuntu):
importance: Undecided → Medium
summary: - tracker-miner-fs-3 crashed with SIGSEGV in g_main_context_dispatch()
+ tracker-miner-fs-3 crashed with SIGSEGV in finish_current_directory()
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tracker-miners (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.