#1020 Liferea uses 100% cpu on specific news items

v1.8
open
None
5
2013-02-14
2012-08-06
No

I was using liferea-1.8.5 on gentoo linux, and following planet.gnome.org found some _news_ entry which when I click on, liferea stops responding (cpu usage 100%) I think only killing the application helps ( specific blogpost which can reproduce the bug pvanhoof.be/blog/index.php/2012/08/06/curiosity (I removed http:// ... don't know about links ...) , later I tried 1.8.7 to see if it is fixed maybe, but still I get the same result on the specific news. Then I thought it uses webkit maybe it's something there and installed midori which uses the same webkit package as liferea (it shows the page without a problem (which doesn't say it's not a webkit problem, I don't want to judge)) . I'm using webkit-gtk (1.6.3 (1.6.3-r200)).

Discussion

  • Anonymous - 2012-08-07

    One small but probably important update, I tested the same feed and news item on liferea-1.8.6 (on fedora distribution), and I cannot reproduce this bug. Then it's probably some other component which liferea uses directly or indirectly.

     
  • Lars Windolf

    Lars Windolf - 2012-08-20
    • assigned_to: nobody --> llando
     
  • Lars Windolf

    Lars Windolf - 2012-08-20

    Thanks for the report. I cannot reproduce the issue, but I'm getting similar reports from other users. Given that there is only an image in the post I'd guess the image rendering is causing the effect.

    Can you try turning the comments for this feed off (check box in feed properties "Advanced" tab)? I'd like to known if this influences the behaviour.

     
  • Anonymous - 2012-09-17

    I tried adding this blog only (not using planet gnome), and it stopped responding again on the same post, later I disabled comments as you recommended, then it worked fine, picture was there. Then I tried again without comments disabled, it was cached somewhere (?) didn't know how to clean the cache, tried by deleting the feed subscription, restarting liferea, then adding it again, and I wasn't able to reproduce it.

    This bug should be closed?

     
  • Anonymous - 2013-02-14

    A lot of things changed in between (software), I cannot reproduce this anymore, and this can be closed.

    Sorry for the noise, thanks!