Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 403951

Summary: =net-news/liferea-1.8.0 pegs CPU at 100% indefinitely on converting a 1.6.x profile
Product: Gentoo Linux Reporter: Jeff (JD) Horelick (RETIRED) <jdhore>
Component: Current packagesAssignee: Víctor Ostorga (RETIRED) <vostorga>
Status: RESOLVED DUPLICATE    
Severity: major CC: iskren.s
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
URL: https://bugzilla.redhat.com/show_bug.cgi?id=786070 http://jeff.ecchi.ca/blog/2011/12/24/investigating-lifereas-startup-performance/
Whiteboard:
Package list:
Runtime testing required: ---

Description Jeff (JD) Horelick (RETIRED) gentoo-dev 2012-02-15 20:27:26 UTC
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.
Comment 1 Víctor Ostorga (RETIRED) gentoo-dev 2012-02-16 15:01:24 UTC
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)
Comment 2 Víctor Ostorga (RETIRED) gentoo-dev 2012-02-16 15:18:32 UTC

*** This bug has been marked as a duplicate of bug 290851 ***