Bug 224740 - akregator unusable since KDE 4.4RC2
Summary: akregator unusable since KDE 4.4RC2
Status: RESOLVED FIXED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-29 11:55 UTC by Marc Schiffbauer
Modified: 2010-06-26 10:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Schiffbauer 2010-01-29 11:55:25 UTC
Version:           1.6.0 (using Devel)
OS:                Linux
Installed from:    Compiled sources

Seems like some big bug has been added from Release Candidate 1 to Release Candidate 2:

Since KDE 4.3.95 akregator is unusable because it is not able to display webpages in tabs properly.

To reproduce:

* Select a Newsitem from the List (heise-News is good for demonstration of the problem)
* Select "complete Article" (link at the bottom)
* The heise.de NEWS-Site will open in a new Tab

Now if you click on a link within the site, the whole tab will stay totally blank and it looks like akregator is trying to load the site but it does not work.

Copying the URL (right click on the tab) and opening the page in a real webbrowser works immediately witout any delay.

This effect has started to show up here since 4.4RC2 and renders akregator mostly unusable for me.
Comment 1 m.wege 2010-01-29 12:15:26 UTC
I can confirm those problems partly. Also that those problems did not exist in RC1, but in RC2. It does not happen on all sites and appears to happen kind of randomly which pages of a site are affect. If a page is affected reload does not help. But loading the same page in konqueror does.
Comment 2 Frank Osterfeld 2010-01-29 12:32:21 UTC
Strange, there were no changes in Akregator between the RC's, so it must be a kdelibs regression.
Comment 3 m.wege 2010-01-29 18:29:42 UTC
Hmm, it appears to me that the problem may be have something to with akregator having "not enough connection slots", if there is something like this. If the problem appear, it does not help, if I reload the tab. But if I close some tabs in akregator (which were already loaded), then new tabs can be loaded. So if there is something like those "connection slots" akregator may not close them correctly or does not realise that they have been closed.
Comment 4 Frank Osterfeld 2010-01-29 18:58:43 UTC
"Connection slots"? Once the tabs are loaded, they should consume that much bandwidth if at all.
one thing that comes to mind are file handles...  Akregator consumes quite a few already, and if there is an additional leak somewhere, things might break.

Maybe you can run the following once you experience the problem again (all one line; googled it, and seems to work).

ps -e|grep -v TTY|awk {'print "echo -n \"Process: "$4"\tPID: "$1"\tNumber of FH: \"; lsof -p "$1"|wc -l"'} > out; . ./out | grep akregator

Additional question:

How many feeds (approximately) do you have?
Do you use akregator standalone or inside Kontact?
Comment 5 Marc Schiffbauer 2010-01-31 13:32:47 UTC
Process: akregator      PID: 7985       Number of FH: 201

I have 12 feeds.
I use akregator standalone.

The URL where it happened right now is:
http://www.heise.de/newsticker/meldung/Apples-iPad-bei-T-Online-ab-630-Euro-mit-UMTS-2-Update-918351.html

Feed is: http://www.heise.de/newsticker/heise.rdf
Comment 6 Marc Schiffbauer 2010-01-31 13:35:38 UTC
Additional note: while having this blank tab, akregator now eats 100% CPU from one of my cores.
Comment 7 Marc Schiffbauer 2010-02-02 16:57:30 UTC
Why is this bug bug still "UNCONFIRMED" ?

I have hit this bug in 4.4RC3 too.

White, empty tab and eating 100% CPU when it tries to load 
http://www.heise.de/newsticker/meldung/Erster-Meilenstein-von-OpenSuse-11-3-mit-LXDE-920282.html
Comment 8 m.wege 2010-02-02 22:42:17 UTC
Hi Marc, I believe the problem does not depend on the page. I tried it, it worked for me. There must me more in it. Seems like you and I are the only ones who have experienced it so far. And for it is not so bad, since it does not occur all the time. That is surely a reason why it is still unconfirmed. It needs to be made reproducable.
- I can confirm high CPU-usage, when the bug occurs.
- I have also noticed an nspluginviewer running, comming from Akregator, even though all tabs containing content were closed.
- The tabs not loading are showing grey
- when I close the tabs that worked until the bug occurs, no kio_http process comming from akregator is showing up in system-monitor. At the same time this works without problem with Konqueror running.
- Killing nspluginviewer does not make a difference
- memory usage is rather high, more than 200000k
- There are nearly 40 kio_http processes which show up as belonging to Konqueror. But there is only one tab now openend (this). I have close the others, but the kio_http-processes remain. I do not know if this is normal. If not there might be a connection.
- There is a kio_http_cache_cleaner. After I kill that, suddendly there are kio_http-processes which were started from akregator. But: The akregator tabs are still not loading. Systemmonitor shows that kio_http_cache_cleaner has restarted.
Comment 9 m.wege 2010-02-02 23:09:08 UTC
I think I have come close to reproduce it now. I closed akregator. Started it from yakuake (Konsole) again. Akregator loaded the tabs from session restauration. Everything fine. Then I closed some of them. And started to open new ones. Then the bug occured. In konsole there is many output about nspluginviewer again. May it has something to do with it. Also: When closing Akregator. In the last moments on screen I saw that one tab had loaded.
Comment 10 m.wege 2010-02-03 17:52:40 UTC
This bug in Konqueror (which was fixed today) might be related:

https://bugs.kde.org/show_bug.cgi?id=224857
Comment 11 Christophe Marin 2010-06-10 17:29:36 UTC
Could one of you reproduce this issue with KDE > 4.4.2 ?
Comment 12 m.wege 2010-06-10 19:48:00 UTC
Yes and no. I that version it happened very frequently and caused many problems. Now it happens sometimes, so rarely, that I forgot to write something on this bug.
Comment 13 Marc Schiffbauer 2010-06-26 10:34:12 UTC
Seems to be fixed. Please reopen or report if this is still an issue.