Shadowlight memory leak

  • Problem Description

    Destroying shadowlight objects or restarting the layout will bloat the used image memory.

    Attach a Capx

    Can be demonstrated with Construct 2 example capxs.

    Description of Capx

    Just using the example capx.

    Steps to Reproduce Bug

    • Just add an event like "on right click -> restart layout" and observe the memory occupation while repeatedly restart the layout.
    • Can also create new shadowlights and destroy them afterwards, same effect. The amount of memory leaked is multiplied by the number of shadowlight instances. Removing the shadowlight object from the layout will result in proper memory cleaning.

    Observed Result

    Memory usage ups a 300-500 kb each restart. Net memory usage of a shadowlight actor is about 800 kb, so it does not clean everything properly.

    Expected Result

    Destroying an instance should free the same amount of memory as creating one.

    Affected Browsers

      Seen in Firefox, Chrome, Nodewebkit in both preview and built versions. IE probably will show the same behavior but honestly didn't test it with a recent version.

    Operating System and Service Pack

    Windows 7 32bit patched to date. Geforce 8800GT patched to date.

    Construct 2 Version ID

    Observed in the latest stable r190 and also r187.

  • Javascript is garbage collected so increasing memory usage is expected until the next garbage collection event, which may not happen predictably. Can you provide a .capx (as per the guidelines - your description does not use an unmodified example file) which does this automatically and clearly proves that the memory is not collected?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Thanks, should be fixed in the next build.

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