Anyone else seeing slower performance with C3 editor on Chrome?

In my case, when I open my project in Chrome, it uses around 3.5GB of memory, and this number doesn't change much with time.

I tried forcing Chrome to use the dedicated GPU, it made no difference. And as I mentioned, the editor still lags on my gaming PC with a powerful graphics card.

I also tried Edge browser, closing all search windows, different editor themes, disabling hardware acceleration in Chrome, disabling spell check, disabling auto-fill for addresses, disabling Windows Defender and many other things. Nothing helps.

Same Large project that's been open for hours (Total blocking time: ~4.3 seconds):

I posted very similar results in this comment.

It still feels like the same problem to me. I'll try to monitor the memory usage more closely, perhaps it is increased with time, but not very dramatically.

The editor is much more likely to lag when the project has been open for several hours. But I've seen it happening just 10 minutes after opening.

Have you tried working on a project that's been opened for a few hours vs. the same one that's been freshly opened?

So I was working for 8 straight hours today without closing the project. I can confirm that there is no memory leak in my case. Chrome memory usage stays at around 3.5 GB. Sometimes it goes up to 5-6 GB (when I open more tabs or preview the project), but eventually returns to 3.5 GB. And it seems to be unrelated to the lagging issue. I first noticed lagging after about 10-15 minutes, and memory usage was at 3.5 GB at that time.

1StepCloser I think I found how to temporarily fix these lags! You can force Chrome to run garbage collection - in DevTools click a little can icon on the Memory tab.

I tested it several times today. Whenever I noticed the editor becoming less responsive, I clicked that button and it immediately stopped lagging. The effect lasted 5-10 minutes in my case.

Please let me know if it works for you!

Awesome dop!

I'll test this out.

dop2000

Is this exclusive to the browser, or does this suggest that the engine itself has issues with garbage collection?

1StepCloser The lag feels a bit shorter, am I right? Do you have lags in the expression editor? They are the worst in my case, after I type something like "lerp(" the browser can freeze for 10-20 seconds sometimes. And clicking the garbage collection icon reduces them to nothing! Can you test with those?

Haven't used C3 some time. But using my "4 dimensional" sense and knowing every C3 UI change triggers editor wide checks!

Past years C3 only had big editor changes in Timeline and stuff that comes with it.

So the question is does your project utilize timeline or its features? Possibility is, UI dialogs are in reality hidden and not closed/inactive. And when any editor change is happening, it still run checks on all hidden dialogs.

While clicking that Garbage delete button, it somehow deletes them from "active" memory and does not run editor change checks on them. But after using editor 5-10min, you could have shuffled though enough dialogs and eventsheets, which puts them all in "active" state and now every editor change will check them again.

SnipG I don't use timelines. And I tried closing all tabs in the project, restarting the editor and only working in one or two event sheets - it still starts lagging randomly. So it doesn't look like the number of open UI windows/tabs is what's causing these freezes.

The good news is that garbage collection definitely helps! Here it reduces 2-3 seconds lag to zero:

SnipG I don't use timelines. And I tried closing all tabs in the project, restarting the editor and only working in one or two event sheets - it still starts lagging randomly. So it doesn't look like the number of open UI windows/tabs is what's causing these freezes.

The good news is that garbage collection definitely helps! Here it reduces 2-3 seconds lag to zero:

Subscribe to Construct videos now

Seems quite apparent at this point, that there is a garbage collection issue, either in chrome in general, or specific to C3.