Help! Thread won't load!

[Fern]

No one on my forum can load this thread. 


It is a character application and thus a member filled out out entirely, is there anyway to access it, and could someone tell me what happened?


Thanks.

[HARP]

I am not sure if it is the problem you are referring to, but I got this error when I opened the page.

[Chris]

Go into your admin panel and disable your STYLE TAGS PLUGIN and the thread should load.

[Fern]

Will I have to keep that disabled for it to load permanently? A lot of my members currently use it...

[Chris]

Once disabled you can then edit the post and try to fix the problem. The post itself cannot be quoted by guests so I cannot really see the BBCODE that was used but the section in that post that starts with "0 Moons:" contains 21 DIVs and 17 of those are nested (meaning one DIV inside of another DIV inside that inner DIV and so on with that going 17 levels deep).
It is generally nestings that goes too many levels deep that causes that plugin to choke, since it uses the memory expensive recursion technique to walk the DOM tree so at some point the stack runs out of memory. Usually when you see nestings like that it is because the post author opened a div ([div]) but neglected to close them with a corresponding div closer ([/div]) so the browser automatically closes it for them all at the end of the post resulting in multiple levels of nested DIVs.

Instead of:


[div] This is DIV #1[/div]
[div] This is DIV #2[/div]
[div] This is DIV #3[/div]




This is DIV #1

This is DIV #2

This is DIV #3

You get (when [/div] is left off):


[div] This is DIV #1
[div] This is DIV #2
[div] This is DIV #3




This is DIV #1

This is DIV #2

This is DIV #3

the javascript engine saves the entire execution context unto the stack each time another recursion function is called and the stack eventually runs out of memory space once it gets too deep. My advice to Bennett 🚀 some time ago was to process the node list from the tail end thus taking advantage of the fact that nodes are returned in document order and you would be working from inner to outer which is obviously the intent of using that recursion but without the expensive memory consumption.

[Bennett 🚀]

Aug 9, 2017 11:07:25 GMT -8 Chris said:

Once disabled you can then edit the post and try to fix the problem. The post itself cannot be quoted by guests so I cannot really see the BBCODE that was used but the section in that post that starts with "0 Moons:" contains 21 DIVs and 17 of those are nested (meaning one DIV inside of another DIV inside that inner DIV and so on with that going 17 levels deep).
It is generally nestings that goes too many levels deep that causes that plugin to choke, since it uses the memory expensive recursion technique to walk the DOM tree so at some point the stack runs out of memory. Usually when you see nestings like that it is because the post author opened a div ([div]) but neglected to close them with a corresponding div closer ([/div]) so the browser automatically closes it for them all at the end of the post resulting in multiple levels of nested DIVs.

Instead of:


[div] This is DIV #1[/div]
[div] This is DIV #2[/div]
[div] This is DIV #3[/div]




This is DIV #1

This is DIV #2

This is DIV #3

You get (when [/div] is left off):


[div] This is DIV #1
[div] This is DIV #2
[div] This is DIV #3




This is DIV #1

This is DIV #2

This is DIV #3

the javascript engine saves the entire execution context unto the stack each time another recursion function is called and the stack eventually runs out of memory space once it gets too deep. My advice to Bennett 🚀 some time ago was to process the node list from the tail end thus taking advantage of the fact that nodes are returned in document order and you would be working from inner to outer which is obviously the intent of using that recursion but without the expensive memory consumption.

I do not ever recall getting this suggestion, but did just do a rewrite of the plugin because I was bored and procrastinating other things. Benchmarks of the new plugin are in the 4-6 ms processing time for each post using style tags, rather than something like a total of 1-2s for all posts on the page with the old plugin.
So Fern , look for the updated Style Tag plugin to be available in the plugin library later this week when the PB staff approves the new v2.2.0.
EDIT: I posted the downloadable plugin file on the support page.

[Chris]

You may have missed it but I am ecstatic to hear of this new version and the benchmarks

support.proboards.com/post/5863210