Do you mind sharing a public url to me that I can test we had issues with this a while back. What I found was the possible problem for the memory leak which was native weweb components like inputs and date finders weren’t disposing of the memory properly when it was unrendered so it kept stacking up everytime we opened the pop up with these types of inputs. Weweb did end up fixing the issue we had at some point as we stopped having users say they’ve crashed but I haven’t checked it again recently.
Here’s the post where I go into what I found a bit more in-depth, might help you find if it’s the same issue or a new one. You might need to do some research on how to navigate the memory snapshot data took me a bit to figure out what I was possibly looking for.
Also on another note my editor has been crashing a lot today.