Steps to reproduce

1.  Modify component template to force a rendering exception, for example add to /mtk/templates/components/html.ftl the following line:

   ${content.noProperty}

1.  Open pages app and create a new page
2. Add some components different from the previous one
3. Add a new component of the modified template

Expected results

Editor shows the exception within the component but the rest of the editor works fine allowing editors keep on working

Actual results

Editor becomes unstable, main area goes to the bottom and new added components are not shown

Development notes

In 5.7.X it works as expected.
This is not reproducible in demo author as the instance needs to be restarted after first run so edit mode is enabled (MAGNOLIA-7044).