Not the case here as it happens every-time I open Wappler now with Beta 19 installed. Was a little more random previously but still a good 90% of the time.
I'm not sure opening with logging enabled will help as there are no errors so to speak. Would this assist with debugging the situation @George?
Wouldn't mind if I was working on multiple Projects at the time of closing Wappler but I'm only working on a single Project. If you want to go ahead and create Bug Report @franse I'm happy to add to it rather than creating multiple Reports on the same issue.
EDIT:
One Window open 'Project open in another window' error...
Is it maybe happening on specific pages? Are those pages cpu intensive?
Does it happen after edits or all the time when you open that page?
What are you editing exactly?
Also try sticking to one main project window to isolate the problem before mixing all kind of problems.
You can also try to do a full clean Wappler install, deleting all the local data - as chrome keeps lots of caching data that can eventually slow things down.
We also have “clear data” option in design view context menu that clears a bit but seems to me a full install from scratch might be best for you.
That way I can start with a clean slate which should give a more reliable baseline to understand what is happening and report more accurately.
Pages are not CPU intensive at all. If it were just the one Project I'd be able to pinpoint it but it is a wide range of page types.
It is pretty consistent in all circumstances. I've half a dozen Projects I switch between of varying types. As with the above answer it happens across the full-board.
From basic Bootstrap pages with little extras just the CDN resources and standard best practices with regards to layouts to complex designs with multiple scripts and styles. All are Node based.
I shall do and report back once I've started with a fresh installation and carried out some house-keeping as recommended in your above reply.
OK have done this to the point that nothing with 'Wappler' in the name appears in grep and did a reboot for good measure. Unfortunately did not change anything but still nice knowing everything is fresh and clean. Even removed Wappler 6.8 as well. I'll wait until the Linux version Electron update rather than post any further. I can still work. I love all the changes. Wappler has never looked better! All Projects are stable and all work fine so not one issue in that regard. Despite the couple of Bugs here and there that don't stop me working am a happy and content Wappler User. Just wanted to say that. Thanks once again @George. Have a great weekend and make sure you take some time off (likewise Patrick and Teodor)!
I mean how do you do the edits? Are you editing in code view or in design view? And what particular code are you editing? Like if you are editing in the root level of the html body, we have to refresh the whole doc in design view on each edit and that might be more memory intensive.
While if you are just editing nested deep html, only the surrounding tag needs to be refreshed.
