Anyone else seeing slower performance with C3 editor on Chrome?

They mention this: "Disabling "Memory Saver" and adding my site to "Always keep these sites active" completely fixes the issue."

I checked my Chrome settings and it had Memory Saver disabled by default. I added *construct.net to the list of active sites, and so far the editor didn't lag today for me!

.

alastair Do you get this error in the editor or in preview? I learned that open tabs in the editor consume a lot of memory, so if you are able to load the project, try closing some tabs in it.

If you can't even load the project, extract all files into a folder and delete all *.uistate.json files. After that you should be able to open it.

I've been using C3 for 3 days now without the editor freezing. I think adding C3 to "Always keep these sites active" list worked for this specific problem.

This should be good enough to keep working normally for now until we wait for a chromium fix.

Awesome to hear dop,

Perhaps the performance issues I deal with are more isolated to projects of the size I'm working with.

Project Version: r332

I've tried with the Memory Saver Toggled On/Off, but this is the current setting:

After reading your post I updated Chrome, but I have data for the previous Chrome version and the most recent:

In Chrome Version: 110.0.5481.104

Project Open For Several Hours

This is how long it took to move a single action from one place to another:

After garbage collection it still took this long:

In Chrome Version: 110.0.5481.178

Project Open For ~30 minutes

This is how long it takes to move a single action from one place to another:

After garbage collection it still takes this long:

Memory footprint is relatively normal:

~2 GB

For me, the only reliable method thus far for maintaining smooth performance is to continually reopen the project every few hours.

Which supports the notion (in my case) that the clearance from garbage collection (unsurprisingly) doesn't meet the clearance from closing the project and reopening it.

Something seems to be stacking up over time that affects performance, but doesn't get addressed by garbage collection that is only noticeable in certain-sized projects:

Other details:

I save quite frequently (every 15 seconds or less if actively making changes).

The save method I use is project folder (It would take several minutes to save changes otherwise, which if I'm saving every 15 seconds...yikes).

I mention this as it could be a potential factor among other actions:

Save

Undo

Redo

Copy

Paste

Etc.

Another note-worthy observation (Cut / Paste):

After updating to the newest version of Chrome, I opened my project and changes made within those 30 minutes included a large amount of cut and paste actions of several events.

I'm inclined to think that might be a factor as the project had only been open for ~30 minutes, yet reflected the performance I see in my project when it's been open for several hours:

In other words:

Occasional cut / paste actions over several hours might resemble the performance impact of large amounts of cut / paste actions in a short amount of time.

I might test this out further and report back.

Fundamental Performance Impact for moving actions:

Testing Environment:

To control for other factors. I closed all tabs, collapsed all project folders, and performed this test on a blank event sheet with only the single action moving from one place to another.

The Test

Moving the action from the bottom event to the top event.

Results

Blank Project with only the testing environment:

Re-Opening my project and doing nothing else but testing the action movement in the testing environment:

Performance Impact:

At baseline this shows that moving an action takes approximately 47 times longer to perform in my project compared to a blank project even when closing all tabs, collapsing all folders, and working with an isolated action in an isolated event sheet.

So this begs the question(s):

• What is C3 checking to perform this action?
• Is C3 looking at various other event sheets to move this isolated action within this isolated event sheet?
• Are objects, project folders, global variables, etc. being checked when moving this isolated action, when on the surface, it appears to involve none of them?

Considering this involves freshly opened projects, garbage collection isn't the focus.

Furthermore, considering that these two tests were performed in the same environment (same background tasks running), this seems to highlight a potential issue.

I'm sure this is quite tricky because there are various factors that need to be checked in some cases when moving events (duplicate variable names, group names, local vs global variable, etc), but perhaps when these checks are made can be optimized?