[Patrics83]

Sorry for the delay...

Here's the output: http://sprunge.us/TAaB

(build #0803)

Yes that confirms OOM, almost certainly due to the unbounded recursion consuming all memory (or maybe just heap).

Although this is obviously an issue, it could also be "by design" (albeit a design that doesn't work well/at all on low memory systems) in which case I'd suggest opening a trac ticket and hopefully a developer familiar with this area can decide if there's a better way of handling recursive slideshows that will work without using all available memory.

Thanks for the advice.
I have now opened a ticket, hopefully someone will be able to optimize the method.