This hardly can be considered as a bug, as in 4.2+ we have made some changes which will detect such issues and throw the OutofMemoryException. If you have a template that is based on another template - it is completely ok, but if the initial template is based on the newer template all pages associated with the second one will throw the error, because of the internal loop that will be caused.
All the best,
the Telerik team
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items