Textbox CPU Usage

0 favourites
  • 5 posts
From the Asset Store
Forget about default textbox restrictions, you can create sprites atop of the textbox
  • Link to .capx file (required!):

    dropbox.com/s/idbzqygq6wp6rdm/textbox_bug.capx

    Steps to reproduce:

    1. load project, run the debugger, no interaction needed

    2.

    3.

    Observed result:

    CPU usage goes to 17% (on my machine). Each text box adds between 5-6% CPU usage each... and it keeps increasing. I've managed to exceed 50% with 10 textboxes. Disabling the textbox makes no difference.

    Expected result:

    a disabled textbox should have no appreciable CPU usage

    an active textbox with no attached events should not be consuming so much CPU time - it's effectively a static structure... eg html forms.

    Browsers affected:

    Chrome: not tested

    Firefox: yes

    Internet Explorer: yes (ie10)

    Operating system & service pack:

    Windows 8 professional

    Construct 2 version:

    R141 (correction, I was actually on R142)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Well I'm getting fps drops using the new version (143) while running my project, that did not occured while running with older versions, but your problem seems to occur with 141 version.. not sure if there is something common about that

  • Correction, I was on R142

    I've just downloaded R143 and I found the textbox impact seems to be similar.

  • I've managed to optimise this a lot for the next build - even a screen full of controls should then only use a few % of engine CPU. However we haven't changed anything to do with these in recent builds so it's unlikely any performance difference in r141-143 is related to this.

  • Thanks Ashley!!

    I'd not have noticed as I've only been a user since R139 (and I've bought a licence too).

    Spotting this would not have been possible if it were not for your excellent debugger and profiler. I'm sure this is not going to be the last optimisation issue that the profiler will help us spot.

    R

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)