This is actually a known issue, and I could've sworn I have answered this particular question myself. The Joomla developers state that this is should be the expected behavior when there is an issue with the cache adapter (most likely this issue is a permission issue on the `cache` folder or the `administrator/folder` - they are not writable by Apache).
We have discussed the issue at length [here][1] - and it has sparked a Twitter discussion on whether this is a feature or a bug. The Joomla development team insists it is a feature that was added for stability reasons (see their reply [here][2]) - despite the fact that the previous behavior did not cause the whole Joomla website to crash (the current behavior does).
The fix is typically simple and it almost always consists of making both the `cache` and the `administrator/cache` folder as writable by Apache.
[1]:
[To see links please register here]
[2]:
[To see links please register here]