1StepCloser's Forum Posts

  • I just wanna chime in and say I haven't seen any issues. How big are your projects roughly?

  • dop2000

    Looks like we might have to condition ourselves to "F12 + Click Collect garbage icon", just as we've conditioned ourselves to "Ctrl + S".

  • 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.

  • 1StepCloser The lag feels a bit shorter, am I right?

    It's significantly shorter, maybe around 50% faster to move actions around after garbage collection.

    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?

    I'll try that next time (Have to wait since garbage collection works ^.^)

  • dop2000

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

  • 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.

  • As advised by Ashley this worked for me,

    Posting here just in case I come upon the issue again:

    1. Uninstall the C3 app.

    2. Close all tabs on Chrome.

    3. Clear all browsing history, cached files, and cookies.

    4. Re-install the app.

    5. Open project.

    6. Try to Export again.

  • Awesome thanks for the reply wink, I'll investigate on my end.

  • Is anyone able to export a build with advanced minification on any project?

    Having issues on my end, it just stays at minifying script, regardless of if it's a blank project or not, and I've tried on multiple browsers.

    *Trying on previous releases (pre-r328) did finally work for me, although it seems much slower than I recall, not sure if there's been a change to the closure compiler (latest update appears to be jan 3, but I've exported since then just fine), or if it's just r328.

  • Tab-specific memory footprints for Chrome: Shift + Esc

  • You probably already spotted this when you clicked on the option in the engine, but it states:

    The maximum spritesheet size to use. Smaller sizes save memory but larger sizes can improve performance

  • > 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.

    Interesting, when you refer to memory usage, are you using the memory footprint number or the memory statistics from task manager?

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • 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.

    Interesting, the performance of my project when just opened is great, it's usually only over the duration of the project being open does this diminish.

    So we might have different problems.

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

  • Here's a comparison of the javascript profile for moving an action from one place to another in two projects:

    This exact same event structure for testing the movement of an action was used in both projects; the action was moved from the top event to the bottom event once:

    Fresh project (Total blocking time: ~0.72 seconds):

    Large project - Just opened (Total blocking time: ~0.85 seconds):

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

    Total blocking time relevance:

    The main thread is considered "blocked" any time there's a Long Task—a task that runs on the main thread for more than 50 milliseconds (ms). We say the main thread is "blocked" because the browser cannot interrupt a task that's in progress. So in the event that a user does interact with the page in the middle of a long task, the browser must wait for the task to finish before it can respond.

    Whenever I experience this particular slowdown it seems to coincide with the projects memory footprint:

    The top row is the project just opened

    The bottom row is the same project that's been open for hours

    I've mentioned this before in another thread, but the difficulty is identifying what causes this memory footprint to stack up.

    I tried to test this by repeatedly using undo / redo, and although it raised the memory footprint about 200 mb it eventually performed what I'd call a garbage dump and the memory footprint normalized:

    Subscribe to Construct videos now

  • Not to be repetitive if it has already been discussed (I feel like I've posted this before), but, I use Chrome on a Win10 Intel CPU laptop, I have a project with over a thousand events, and I only experience lag when I am in the event sheet view and have hundreds of events visible. I have all events in groups, so I can right-click>event sheet view>collapse all groups, and performance jumps up significantly.

    Also, many yonks ago when I bought my gaming laptop, I noticed C3 performed awfully in Chrome and better in Firefox. Turns out it was Nvidia settings affecting this, as nvidia forces Chrome to use the integrated graphics, rather than the dedicated GPU. It actually prevents you from forcing Chrome to use the GPU, so I ended up disabling my integrated graphics in my laptops BIOS, and all has been smooth ever since.

    Hope this is useful to someone!

    Thanks for the input!

    I've seen group collapsing of benefit for performance, however there appears to be some issues independent of that. (video below is an example)

    I have a project with over a thousand events

    I don't recall having any performance issues when my project was around this size, but earlier in this thread when I referred to larger projects, I was referring to around 15k+ events. Perhaps there's a threshold or the issues scale with project size.

    I only experience lag when I am in the event sheet view and have hundreds of events visible

    Here's an example of how the # of events displayed in a sheet is likely a separate issue (although still relevant):

    Subscribe to Construct videos now

    I ended up disabling my integrated graphics in my laptops BIOS, and all has been smooth ever since

    Nice solution!

    My PC only has a dedicated GPU, but as you said, hopefully this info helps someone!