Hello everyone, I’m having serious problems with page crashes and errors due to excessive memory consumption. Every 2 minutes the editor page gives an error in the browser due to excessive memory consumption. My computer is an 8gb M1 2021 imac and I’m using a new Opera browser (in Chrome this error happens all the time).
This problem is very sad, because it is making it impossible for me to work on my application. I have already used numerous strategies to try to get around this problem (closing applications that consume memory, using another browser only with the web editor tab open). It seems to me, will I have to buy a new computer with a lot more memory to use the weweb? This is an extremely critical point for using the tool. You have an incredible product that is giving me invaluable value, but in this way it makes it very unfeasible to use.
What solution do you recommend to solve this problem?
Error:
The message on the screen is in Portuguese, and it translates to:
“The page crashed
Unfortunately, something caused this page to be terminated. It might have been a conflict with extensions or some other reason.
Try to reload the page or navigate to another page to continue.
Reload the Page”
What I observed occurs when there are many components, something from the editor that is using a lot of memory resources. Simple pages, that doesn’t happen.
This error occurs almost all the time:
in the view of the application under test
when making a display configuration type in the slider component
sometimes the debug view (that is automatically opened on preview) slows down the editor if you have a long list of logs. closing the left side panel before going into preview can be a temporary fix
a suggestion for the team (@luka) regarding the debug panel: a virtualized list or being able to set a maximum amount of log items can be very helpful.
Many times I need to check the value of a variable and I am forced to open the debug panel and the whole editor freezes because is loading the logs. Sometimes there are so many that the only solution is to kill the browser.
My project will regularly be up to 5-7 gb memory usage in Chrome, if i’m working with it a few hours. So every 2 hours I close the browser tab and start up again, and will start climbing from 120 mb in the start to 5-7 gb again. Around 6-7 gb it always crashes, even if I have 32 gb RAM, with over 10 to spare.
So I believe 8gb memory on your computer will make RAM be written to disk, and it will cause serious slowdowns and crashes.
In the last few days, mines gone from working perfectly to unusable! Anyone else experiencing this?
I’ve just noticed the Console is flooded with errors. They don’t start initially, but then randomly it’ll trigger out of control. It seems to be tracking the mouse movement and throwing 1000’s of “Uncaught TypeError: Cannot read properties of null (reading ‘tagName’)”
I haven’t setup any kind of workflow to track mouse position!!
Has a bug has been introduced?
The memory just keeps going up and it was on 4gb before I refreshed the page.
Maybe a coincidence, but I have recently noticed the page and side bar is jumping around more (page scrolling to view elements and menu moving items up and down) than it used to before. I find this annoying as it slows down how I interact and I keep clicking the wrong item in the menu as there’s lag on the movement.
Basically, everytime you try to do something “resource intensive” on the app, editor crashes.
I tried to open a bug ticket awhile ago but was told they can’t replicate the problem. To be fair, I can’t replicate the problem too, but it keeps happening randomly T.T
So yes, it keeps happening, and crashes are still happening. When that happens, gotta reload and refresh and everything is back to normal.
if you are on windows its probably something to do wit h your virtual memory, you probably made some bad edit to it! reset and it should solve it! had this issue for link a month, hated every moment of it!
