Bug 145674 - Akregator becomes slow after opening some 10 tabs with "Complete Story" links
Summary: Akregator becomes slow after opening some 10 tabs with "Complete Story" links
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2007-05-19 14:57 UTC by Aad Rijnberg
Modified: 2018-10-27 03:36 UTC (History)
1 user (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 Aad Rijnberg 2007-05-19 14:57:46 UTC
Version:           1.2.6 (using KDE KDE 3.5.6)
Installed from:    Fedora RPMs
OS:                Linux

I use Akregator to browse through the articles with the "+" on the numerical island (next unread article), and click on "Complete Story" for the news that has my interest, resulting in new tabs being opened. After some 10 articles have been opened in separate tabs the processing of keyboard events (e.g. pressing the "+" for next articles) becomes slower and slower. When I press e.g. 5 times on "+" then it takes some 10 or 20 seconds before the window is updated and the article is highlighted that belongs to 5 unread items further. I suppose this behaviour is not intentional?!
Comment 1 Adrián Chaves (Gallaecio) 2012-10-27 20:49:24 UTC
Do you keep suffering these performance issues in a newer version of Akregator?
Comment 2 Andrew Crouthamel 2018-09-23 02:37:46 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-27 03:36:34 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!