Construct becomes quite sluggish after a while of working

Post reply
0 favourites
  • 9 posts
From the Asset Store
Target 2.0 Slot HTML5 Construct 2 and Construct 3
$15 USD
Casino? money? who knows? but the target is the same!
bellborn's avatar
bellborn

  • But I don't really know why. I mainly wonder if anyone else noticed that. Here's what I do know:

    • It does take a while to be noticable, but it seems to get more sluggish the longer I'm working
    • Simply restarting the editor solves it
    • I wasn't doing much work in eventsheets, mainly saving, previewing, duplicating/adjusting a bunch of replicas across a handful of layouts
    • The project isn't exactly huge overall
    • I have a beefy pc so that shouldn't exactly be a problem
    • The lag is very noticable when: Switching tabs, selecting instances, moving instances

    Considering that simply taking 10 seconds to restart Construct fixes it I'm not even sure if it's super worth to investigate. However, I'm not 100% certain if that was a problem before todays update r421. I feel like I didn't have that issue in r420 but I cannot tell for sure.

    There also used to be a bigger thread about this 3ish years ago, possibly related?

    construct.net/en/forum/construct-3/general-discussion-7/anyone-seeing-slower-167843

  • If you encounter this again you could start the chrome dev tools profiler, that may give a hint at some memory leak or something.

  • Is the editor just generally sluggish/slow, or does it freeze completely for several seconds after certain actions? (I had this issue in the past)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I encountered an issue where the editor would completely freeze for several minutes before resuming and working flawlessly again. This happened with a fairly large project (approximately 1,500 events and 2,000 lines of JavaScript). Interestingly, the freezing only occurred when positioning objects in the layout. While working in the event sheet, the editor never froze, though it did feel noticeably slower, especially when deleting events.

    To potentially improve performance, I tried organizing events into groups and keeping only the group I was actively working on open. While I think this made navigation a bit smoother and may have reduced some of the sluggishness in the event sheet, I’m not entirely sure it had a significant impact. It could be worth experimenting with, but the results might vary.

  • If you encounter this again you could start the chrome dev tools profiler, that may give a hint at some memory leak or something.

    Yeah I will do that. It's bound to happen again. I kinda forgot that this profiler exists, but I did take a video for comparison yesterday with two editors open side by side. Left one being freshly opened, right one being the sluggish one. I wouldn't say there were outright freezes, but I could imagine it getting so sluggish that it would be considered "frozen". The only freezing I had was when zooming the layouts, there it would sometimes not do the zooming despite the scrollbars indicating I was indeed zooming. Eventually it would then snap out of it and display the correct zoom again.

    Subscribe to Construct videos now

    I don't believe it has much to do with the eventsheet because I was barely doing anything in the eventsheet at that point. I also have everything well grouped though, but if there would be an inherent problem with the eventsheets or objects or layouts, restarting shouldn't fix it I think.

    I just have 288 events with 259 conditions and 607 actions. 58 Object types and 9 Families, 19 layouts and 5 eventsheets. That's like a baby-project.

  • Is the editor just generally sluggish/slow, or does it freeze completely for several seconds after certain actions? (I had this issue in the past)

    This happens to me often and it's very annoying. Did you find the solution?

  • This happens to me often and it's very annoying. Did you find the solution?

    I believe that was a Chromium issue and it kinda fixed itself with the next Chrome update. Here is my old post, you can see the video in the first comment:

    construct.net/en/forum/construct-3/general-discussion-7/help-editor-randomly-lagging-173900

  • Okay, thank you.

  • Looks quite like it's a similar (the same?) problem that it was back then. Maybe. There's lots of removeChild and appendChild listed, which seem to somehow rise in numbers when Construct is actively used.

    Compared to the same interaction (drag & drop) in a freshly opened editor.

    I saved the profiler traces if it helps but Ashley mentioned in the other thread that they are not really helpful due to obfuscation, but I can post them if needed. The delay always happens on pointer interaction, like when selecting an instance on the layout. So something is ballooning there the longer Construct is in use.

Post reply
  • 9 posts
Return to board index
Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)