Summary: | Javascript problem on Digg.com | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | dave <flyinsquirrel992> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | adawit, ambrop7, jlp, mursusoft |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
dave
2007-07-15 06:12:00 UTC
In KDE 4.0.0 Konqueror gets the data, but the comment doesn't slide open until you scroll the Konqueror view. 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? 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. 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). *** This bug has been confirmed by popular vote. *** Still happens with kde 4.3 beta 2 Digg changed their site and with new Konqueror and new site this appears to be working just fine. 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. |