Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tracker-miners
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 61
    • Issues 61
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • tracker-miners
  • Issues
  • #187

Closed
Open
Created Dec 19, 2019 by Jose Riha@jose1711

an unfinished/corrupted midi file puts tracker out of service

I have found that one of the files on my harddrive makes /usr/lib/tracker-extract consume the whole CPU while not making any progress. The file is a midi (.kar) file which timidity plays fine but after some minutes reports Terminated sig=0x02.

To reproduce:

  • copy the attached file White_Room.kar to any of the directories watched by tracker
  • observe system behaviour
$ tracker daemon
..
0%  Extractor               - Extracting metadata 
$ htop

Removing the file and restarting extract service (systemctl --user restart tracker-extract.service) fixes the problem.

Tracker: 2.3.0 Arch Linux: current, x86_64

Assignee
Assign to
Time tracking