Answering my own question: Seems it had nothing to do with Discourse after all.
A certain combination of params sent the web component into an scheduleUpdate loop.
Sorry for the noise.
For reference, here’s what I did:
- Used a non-minified version of rapidoc in the theme component
- Used the debugger while the site was stuck
- Looked at the call-stack & found the culprit triggering repeated updates (
show-curl-before-try) - Changed rapidoc’s params not to trigger this scenario anymore
If you feel this topic doesn’t add to the discussion/is irrelevant, feel free to remove.
Thanks anyway and sorry for the noise again