The problem for me seemed to have been caused by having a single very large PDF on my Desktop. Even after stopping hud-service from executing I noticed that nautilus was consistently using 15% of one CPU core, but as soon as I moved that PDF somewhere else the problem went away. I've now allowed hud-service to run again, rebooted, and things appear to be working nicely again.
Observations:
- Why is generating the preview icon for a large PDF so costly? Surely only the first page should be read and used for that purpose?
- Surely these preview icons should be cached?
- I think even if generating the preview icon is expected to be costly, there is a bug here as there is definitely a memory leak + the CPU usage stayed consistently high for hours. Surely the process should finish and then the CPU usage should drop away again?
The problem for me seemed to have been caused by having a single very large PDF on my Desktop. Even after stopping hud-service from executing I noticed that nautilus was consistently using 15% of one CPU core, but as soon as I moved that PDF somewhere else the problem went away. I've now allowed hud-service to run again, rebooted, and things appear to be working nicely again.
Observations:
- Why is generating the preview icon for a large PDF so costly? Surely only the first page should be read and used for that purpose?
- Surely these preview icons should be cached?
- I think even if generating the preview icon is expected to be costly, there is a bug here as there is definitely a memory leak + the CPU usage stayed consistently high for hours. Surely the process should finish and then the CPU usage should drop away again?