TL;DR : editor crashes in test mode because of real-time update that comes into the logs
I’ve got some issues using the editor because we are in a testing phase and a lot of users are testing the application, making a lot of changes on the real-time updates.
And those updates come into the logs on my editor and it really slows down the application, the editor, and also makes the editor crashes.
So I’m wondering how I can deal with that problem ?
Has anyone had that before ?
Hi Matt 
that’s a really unfortunate issue you are having.
I’m going to activate out tech team and I’ll let you know if they come up with an answer.
For next time I recommend using our support chat for this sort of issues:
Thank you for your patience!
We have delt with this before, we didn’t find a full solution but some helpful things were hiding the logs most of the time or only showing errors and clearing them regularly
for what is worth this has been a problem since the feature was added: The page crashed error (insufficient memory) - CRITICAL ERROR - #7 by dorilama
it would be great to be able to opt out the log panel: an option to only log into the browser’s console where we can already manage what to see and when to see it, and it’s light on resources.
Hi @Matt
We don’t have any similar reports for now. Can you please make a screen recording showing the issue? Thanks!
