Bug 381415 - balooctl chokes and uses 100% cpu on oddly named folders
Summary: balooctl chokes and uses 100% cpu on oddly named folders
Status: RESOLVED FIXED
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.34.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-19 20:45 UTC by Samantha McVey
Modified: 2020-10-26 16:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Tar archive of the empty folder with an odd name (10.00 KB, application/x-tar)
2017-06-19 20:45 UTC, Samantha McVey 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Samantha McVey 2017-06-19 20:45:29 UTC 
Created attachment 106172 [details]
Tar archive of the empty folder with an odd name

Baloo will use 100% cpu and not stop until it is killed when trying to index this folder. I have attached a tar archive which contains an empty folder with an unusual name.

Associated journalctl error:
Jun 19 13:32:41 sabayon baloo_file[1502]: org.kde.baloo: Failed to create watch for "/home/samantha/git/rakudo/t/spec/new2/\u0006�" No such file or directory
Comment 1 viniciusbr 2019-01-29 18:45:03 UTC 
I found a similar problem with baloo 5.54.0 with kde neon 5.14 in a fresh installation. Baloo was consuming 100% of the cpu. I disabled it and the cpu back to normal.
Comment 2 Nate Graham 2020-10-26 16:37:32 UTC 
This won't happen anymore. Instead it will skip that folder.