Bug 100711 - Article display falls into infinite loop
Summary: Article display falls into infinite loop
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 1.0-beta8
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-03 08:15 UTC by Will Mitchell
Modified: 2005-04-25 00:36 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
The trimmed feed archive (1.76 KB, text/html)
2005-03-03 08:16 UTC, Will Mitchell
Details
The original feed archive (414.73 KB, text/html)
2005-03-03 08:18 UTC, Will Mitchell
Details
One of the two states (141.97 KB, image/png)
2005-03-03 08:20 UTC, Will Mitchell
Details
The second of the two states. (141.03 KB, image/png)
2005-03-03 08:23 UTC, Will Mitchell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Will Mitchell 2005-03-03 08:15:38 UTC
Version:           1.0-beta8 (using KDE 3.3.2,  (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-6)
OS:                Linux (i686) release 2.6.8

I was reading the RSS feed from Techdirt.com when I came across a bug. I opened one of the articles and it kept flashing. It appears as if the program was trying to decide how to do the word wrapping and falling into an infinite loop. This only occurred in the "Normal View". Widescreen and Combined had no issues at all.

I then went to ~/.kde/share/apps/akregator/Archive and made a copy of the archived feed to possibly use to make a test case. After making a copy of the feed, I exited the program to restart to establish the bug was reproducible. I got the exact same problem. I then began to cut down the archived feed to attempt to isolate the article causing the problem. I was successful in cutting it down to a specific article.

I will attach the feed I trimmed down too, the original feed I started trimming from, as well as two screenshots. A single screenshot inherently can't show the bug, however if my hunch is correct that it is somehow choking on where to wrap words, the size of the display area then becomes relevant. I was lucky enough with Ksnapshot to get a screenshot of both states between which the program alternated. If it is the word wrapping it would also explain why the bug only appeared in Standard view but not the other two because they all display the article with different widths, unless of course there is something internal to aKregator with regards to the display (I am unfamiliar with the internals of aKregator).
Comment 1 Will Mitchell 2005-03-03 08:16:52 UTC
Created attachment 9939 [details]
The trimmed feed archive

This is the trimmed feed as mentioned in the original report.
Comment 2 Will Mitchell 2005-03-03 08:18:41 UTC
Created attachment 9940 [details]
The original feed archive

This is the original feed archive prior to trimming as described in the
original report.
Comment 3 Will Mitchell 2005-03-03 08:20:03 UTC
Created attachment 9941 [details]
One of the two states

This is one of the two states that the display alternated between.
Comment 4 Will Mitchell 2005-03-03 08:23:01 UTC
Created attachment 9942 [details]
The second of the two states.

This is the second of the two states that the display alternated between.

I suppose I should also mention that the switching between the two states was
very rapid. I'm currently using a laptop, and I could hear that the processor
was being taxed doing this because the extra fans kicked in.
Comment 5 Frank Osterfeld 2005-03-03 08:38:38 UTC
Thanks for that detailed bug report!
I can't reproduce it here, using 3.4 branch. It would be useful to know, if you can reproduce the bug with 1.0 beta10.
We changed the HTML rendering a bit, so maybe this is fixed in beta10. 
Or it's a KHTML bug fixed in KDE 3.4.
Comment 6 Will Mitchell 2005-03-04 03:45:52 UTC
I'll upgrade this weekend and let you know if I can still reproduce the bug.
Comment 7 Eckhart Wörner 2005-04-24 23:48:28 UTC
I can't reproduce it with KDE 3.4 or HEAD.
Will: Have you upgraded yet? ;-)
Can you reproduce it?
Comment 8 Will Mitchell 2005-04-25 00:36:33 UTC
I'm sorry about that, I thought I went back and commented again. My classwork seems to be making my memory fail me.

Anyway, I'm currently using 1.0 beta10 (It is what Debian has in testing at the moment) and I can no longer reproduce the bug. The version of KDE now is 3.3.2.

I have no clue what fixed it, but it doesn't happen anymore.