Request #1587
From:
Account Type:
Free Account
Dreamwidth:
Time posted:
Wed, 20 May 2009 06:40:43 GMT (835 weeks ago)
Status:
closed (1 point to ![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
wyntarvox)
wyntarvox)
Summary:
More than 50 sequential comments break the stylesheets
Original Request:
A comment thread with more than 50 sequential threaded comments (that is, each comment is a reply to the one previous) returns an error:
Error running style: Died in S2::run_code running EntryPage::print(): Excessive recursion detected and stopped.
Nothing beneath the broken thread loads, including other existing comments on the entry. This occurs both in Transmogrified and the style I'm currently using based on Tabula Rasa, but not in the light style (?format=light).
Not sure if you need an example, but here's the link anyway just to be safe: http://azsapphire.dreamwidth.org/15638.html
Diagnostics: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.10) Gecko/2009042315 Firefox/3.0.10
Error running style: Died in S2::run_code running EntryPage::print(): Excessive recursion detected and stopped.
Nothing beneath the broken thread loads, including other existing comments on the entry. This occurs both in Transmogrified and the style I'm currently using based on Tabula Rasa, but not in the light style (?format=light).
Not sure if you need an example, but here's the link anyway just to be safe: http://azsapphire.dreamwidth.org/15638.html
Diagnostics: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.10) Gecko/2009042315 Firefox/3.0.10
Dear starrarte,
This error is deliberate and will happen in any S2 style you use. Since S2 styles can include custom code, all code in an S2 style is checked and prevented from creating infinite loops. If a piece of code gets stuck in an infinite loop it can cause serious trouble on Dreamwidth's servers.
To prevent this, Dreamwidth stops processing a style once something in its code has hit more than 50 loops, like printing the 51st comment in a single thread. As you've discovered, you can still view all of the comments using ?format=light. You can also view them if the style displays entry pages in the site scheme format. This is because these displays are controlled entirely by Dreamwidth so there's no need to check for infinite loops.
I do understand, however, that there's no obvious indication that if you make the 51st comment in a thread that you'll break the rest of the entry for everyone else. I've passed this information on to Dreamwidth developers for discussion on whether or not this infinite loop check can be improved at all. However, I can't make any promises as to whether this will happen.
Regards,
Wyn
This error is deliberate and will happen in any S2 style you use. Since S2 styles can include custom code, all code in an S2 style is checked and prevented from creating infinite loops. If a piece of code gets stuck in an infinite loop it can cause serious trouble on Dreamwidth's servers.
To prevent this, Dreamwidth stops processing a style once something in its code has hit more than 50 loops, like printing the 51st comment in a single thread. As you've discovered, you can still view all of the comments using ?format=light. You can also view them if the style displays entry pages in the site scheme format. This is because these displays are controlled entirely by Dreamwidth so there's no need to check for infinite loops.
I do understand, however, that there's no obvious indication that if you make the 51st comment in a thread that you'll break the rest of the entry for everyone else. I've passed this information on to Dreamwidth developers for discussion on whether or not this infinite loop check can be improved at all. However, I can't make any promises as to whether this will happen.
Regards,
Wyn
Go to: previous open request, next open request
Return to the list of open requests.
Back to the Support Area.