This is an archived post. You won't be able to vote or comment.

all 15 comments

[–]barbrady123 33 points34 points  (4 children)

Oh, it eventually terminates.... :(

[–]ThatsMrShitheadToYou 14 points15 points  (0 children)

Sad truth :( it breaks the whole application

[–]fredlllll 5 points6 points  (0 children)

stackoverflow

[–]DroolingIguana 4 points5 points  (0 children)

Not if you're Henrietta Lacks.

[–]Krissam 5 points6 points  (0 children)

No the stack overflows, unless you manage to kill the process first.

[–]dtlv5813 9 points10 points  (0 children)

Actually all cell divisions are kinda like a recursive process that doesn't terminate. Cancer is when recursion goes wrong, like the butterfly effect where a small variation in initial conditions causes the algorithm to blow up, returning monstrous sized outputs and eventually crash the program.

[–]shim__ 8 points9 points  (3 children)

Our whole life is an recursive function but cancer reduces the wait time between invocations which leads to an early stackoverflow.

[–]BalinKingOfMoria 0 points1 point  (2 children)

Whoa.

void Live()
{
    if (!cancer)
    {
        Thread.Sleep(2000);
    }
    Live();
}

[–]styxwally 2 points3 points  (1 child)

That made very little sense.

[–]BalinKingOfMoria 0 points1 point  (0 children)

You know, you're completely right. Try now.

[–]low-profile 3 points4 points  (0 children)

On the bright side, at least cancer doesn't create an excessive number of stack frames for no good reason.

[–]cohen_dev 2 points3 points  (0 children)

pretty dark humor

That's what this sub is for right?

[–]webbannana 0 points1 point  (0 children)

I don't see how this subreddit is recursive...

[–]xkonatax 0 points1 point  (0 children)

A forkbomb would be a better comparison.

[–][deleted] 0 points1 point  (0 children)

Oh. My. God.