| Summary: | balooctl chokes and uses 100% cpu on oddly named folders | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | Samantha McVey <samantham> |
| Component: | Baloo File Daemon | Assignee: | Pinak Ahuja <pinak.ahuja> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | nate, viniciusbrbio |
| Priority: | NOR | ||
| Version First Reported In: | 5.34.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Tar archive of the empty folder with an odd name | ||
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. This won't happen anymore. Instead it will skip that folder. |
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