Now Sporking: Family Matters, Part 3/[???]

"Wait, yer tellin' me y' decided, outta nowhere, t' restart th' spork NOW?" the sandy-haired adolescent complains, abruptly dumped into the sporking room.

Yep.

"We did get over a month off," his magenta-haired companion points out, dusting herself off as she rises from the floor.

"Too bad! Look at th' Little Miss Mary sporkers! Now there's a spork that ain't EVER goin' t' be finished!"

Are you seriously comparing Cori Falls, even at her worst, to Little Miss Mary?

He pauses, biting his lip, and then shakes his head. "Aw no. No, no, no, no, no." He raises his hands in a defensive gesture. "You ain't gonna make me spork ANYTHIN' resemblin' THAT fic."

Good. Now that we're clear...

ONE FOR THE MONEY!
TWO FOR THE SHOW!
THREE TO GET READY!
AND HERE! WE! GO!

( Short this time, due to bizarre formatting errors and Mozilla memory leaks. )

So I panicked and closed a ton of tabs because I thought Firefox was memory-leaking due to Tumblr...

...and it turns out that the HTML formatting for the spork had privately gone bonkers, leading to what should have looked like THIS:

<span style="color: rgb(0, 204, 255);">Jerry: Glargh. MORE sappy Aesops?</span>

instead looking like THIS:
<span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);"><span style="color: rgb(128, 0, 0);"><span style="color: rgb(0, 204, 255);">Jerry: Glargh. MORE sappy Aesops?</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span>

I wish I was joking.

So the ridiculous formatting chewed up an unholy amount of memory, and the "memory leak" fixed itself once I edited the formatting to no longer look like it had been vomited forth by a chatbot having a seizure.

Just a warning in case you experience a sudden browser slowdown while editing a rich text post that uses a lot of colors. Check the HTML tab - it may save you a lot of time and hassle.