Summary: | needs long time to open links contained in feeds | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | Armin Berres <armin> |
Component: | internal browser | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | asgard.sg1, finex, kde, kmm, lehoangphuongbg, maxi, semajdent |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Armin Berres
2008-11-04 23:18:30 UTC
Version is 1.3.3 right now btw. Can't select this specific one in Bugzilla. Oki doki, I just noticed that in university aakregator is a lot faster. Maybe akregator triggers something like #162600? I have completely disabled ipv6 though. Maybe i should fire up wireshark... *** Bug 193682 has been marked as a duplicate of this bug. *** I'm not able to reproduce anymore using KDE SC 4.4.4: the tab is quickly displayed (empty) and after the page is loaded. I still experience this in 4.4.4 sometimes. Usually the tab opens instantly, but once in a while it takes few seconds. Don't know what it depends on... I'm still seeing this is 4.4.4, too. In my case, it happens every time I open a link. (Also, my internet connection is likely quite slow in comparison.) The problem lies in the overly complicated operation for creating a new tab. This is not because it waits for the website is to be ready but rather there are too many underground operations needed to complete before a new tab is created. *** Bug 142704 has been marked as a duplicate of this bug. *** This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |