I have this weird behavior in a specific page where the debugger doesn’t work at all and native actions like a group focus closing when you click outside of it not don’t work.
I came to a point where I figured the issue was with an specific reusable element, I placed this reusable element in an blank page and whenever it is in the page, this happens.
I completely cleared this reusable element where it’s just a group with anything else inside (no workflows, custom states, properties, html, elements, nothing) and also tried testing with plugin and html disabled on the page and removed any headers.
Just the simple fact the reusable element exists causes this issues on the page and errors in the console.
It’s been nine days since I opened a bug report with no answers, so maybe anyone that has stepped into this could give an idea? I already tried duplicating the element.
Recreating it as a new fresh reusable would be annoying 
Hi @Isaque_Galvao ,
Please ensure your reusable element has any plugin?
From your screenshot, i can see that some element is null and which is throwing these error.
If you are okay then, can you share the link of your new page? let me check and provide the solution.
What is aybee.ai? That seems the issue. Is that a plugin or did you use custom code for it to try and use a package from them?
The error itself says it doesn’t come from a plugin
I cleared everything in the reusable element: plugins, elements, scripts in the header and body, and HTML; I also placed it in safe mode on a clean page, and the reusable element was completely empty inside as well.
I got tired of waiting for Bubble to answer me after 10 days, so I had BuildPrint recreate the reusable element inside a new one. (Duplicating or copying the element also caused these issues.) I created a new, empty reusable element and had BuildPrint reconnect everything.
Hi everyone,
I am also experiencing the exact same issue. Every time I try to open or edit Reusable Elements in the Bubble editor, the browser tab instantly freezes and crashes (“Aw, Snap!”, page unresponsive error).
Browsers tested: Google Chrome and Microsoft Edge (both crash).
I hope the team can help us fix this urgently, as it has been going on for a few days now.
I’m not sure if it is the same issue Sara, I was experiencing issues with the debugger and some other actions not hapenning correctly, yours seem to be worse.
I was able to figure out what element was crashing the page by placing each element in a blank page and checking the console and other issues I had, maybe you could try the same thing.
