Bug 147880 - Javascript problem on Digg.com
Summary: Javascript problem on Digg.com
Status: RESOLVED NOT A BUG
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-15 06:12 UTC by dave
Modified: 2012-01-03 21:57 UTC (History)
4 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 dave 2007-07-15 06:12:00 UTC
Version:           3.5.7 (using KDE 3.5.7, compiled sources)
Compiler:          Target: i586-mandriva-linux-gnu
OS:                Linux (i686) release 2.6.18.8.tex5

basically, while attempting to "Show replies/comments" using diggs new coding, konqueror gets the data from the server and the Comment slides open, but closes instantly, the second time it stays open.

To reproduce this bug go to:
      http://digg.com/
click on any topic (Yellow Diggs box), scroll down to comments, and try to show comments/repies.
Comment 1 Jure Repinc 2008-01-06 15:14:49 UTC
In KDE 4.0.0 Konqueror gets the data, but the comment doesn't slide open until you scroll the Konqueror view.
Comment 2 Ambroz Bizjak 2009-01-09 00:01:55 UTC
In KDE 4.1 and 4.2, comments work only if there aren't too many of them. If I click on one of the top stories, no comments show up, and clicking on the bug icon shows this javascript error:
RangeError: Resource exhaustion trying to perform regexp match.

I guess it's hitting some memory limit. Perhaps it can be enlarged?
Comment 3 Maksim Orlovich 2009-01-09 02:13:44 UTC
Not in a sane way. The limit is based on what the stack size limit is on most systems. If it's not set, libpcre will run out of stack space and crash. The only real solution would be for digg.com to use better regular expressions.
Well, I could also not throw an exception when this happens, but then the script would be only half-running.
Comment 4 Ambroz Bizjak 2009-01-09 10:23:46 UTC
I've increased the stack size with "ulimit -s" from 8192 to 32768, but it doesn't change anything. I also noticed that sometimes there is no javascript error, but only some of the comments load, others either missing or not "fully loaded" (username and digg up/down buttons missing).
Comment 5 mursusoft 2009-04-08 23:40:35 UTC
*** This bug has been confirmed by popular vote. ***
Comment 6 mursusoft 2009-06-24 15:06:18 UTC
Still happens with kde 4.3 beta 2
Comment 7 Jure Repinc 2010-12-19 23:23:39 UTC
Digg changed their site and with new Konqueror and new site this appears to be working just fine.
Comment 8 Dawit Alemayehu 2012-01-03 21:57:48 UTC
Closing based on comment #7. Also could not reproduce the issue with either one of the browser engines in the latest stable KDE version, v4.7.4 or higher.