When having liferea-1.8.0 auto-convert a 1.6.x profile to 1.8, it pegs the CPU at 100% till the process is killed (by hand, using kill -9, doesn't respond to SIGTERM). Then, when liferea 1.8.0 is restarted, there's a bit of I/O wait for a minute or 2 and everything from then on is fine. IMO, this feels like a fairly large issue since this is/will be a fairly common use-case, i'd think. Reproducible: Always Steps to Reproduce: 1. Create a 1.6.x profile with several feeds and feed items 2. Upgrade liferea to 1.8.0 3. run liferea and it will attempt to convert your 1.6 profile to 1.8 and the issue should manifest itself. Actual Results: pegged CPU, had to kill the process Expected Results: converted the profile without needing to kill and restart the process.
If you are still experiencing this issue, please execute liferea using the --debug-all parameter and attach it here, please. Also, keep in mind that liferea 1.8 now VACUUM its sqlite db at startup, so if you had never "vacummed" it before, it'll take some time to start things up. You might also want to try using eatmydata -- liferea (which it disables fsync on your filesystem for that application)
*** This bug has been marked as a duplicate of bug 290851 ***
