What the flying fuck is going on? Normally a cache clear would solve this sort of problem in my experience. Using Quick Node Clone, I can completely clone the problem node, delete the old node this fixes the problem. Disabling site-wide blocks make no difference as I wrote above I can even change the theme and no difference. The last process in the 256 is always str_replace(Array, Array, 'SELECT cid, data, created, expire, serialized, tags, checksum FROM WHERE cid IN ( :cids_0 ) ORDER BY cid') (Line: 343) I think I’m just seeing the usual render queue. Several twig renders are in that queue, naturally, but clearing Twig cache doesn’t fix the problem. If I have xdebug on, the page views will crash because they run over 256 processes. Clearing caches, rebuild menus, reinstall modules nothing fixes it. I can save a new revision on the node and delete the old one doesn’t fix. As I wrote above, *any* page crashes - not just the node’s page. I can edit the node, delete the contents of every field, save over the revision or create a new revision the site still crashes. There is no weird HTML or PHP in the node’s fields. If I delete the node, everything is back to normal. That is, any page outside of /admin which doesn’t use the admin theme. Short version: a single node is causing the whole site to run out of memory rendering any content-related page. I have a content-related WSOD and I’m looking for a little help understanding if there’s anything else I should be looking into regarding rendering or caching to clear the problemĭrupal 8.9.13 contrib modules such as Paragraphs.

Drupal quick node clone