Memory leak in "collmemory" after a relaunch+reload

0 favourites
  • 4 posts
From the Asset Store
A sound pack containing 132 laser gun sound effects, including mono and stereo versions of audio files.
  • Problem Description

    Memory leak (or save file leak?): the "collmemory" section of a savefile gets larger and larger after the game has been closed, relaunched and loaded from a savefile.

    Attach a Capx

    https://dl.dropboxusercontent.com/u/313 ... empty.capx

    Description of Capx

    Spawn objects that are destroyed on collision with another object. The capx also autosave every 1 sec and output the savefile to the browser console.

    Steps to Reproduce Bug

    • Launch the game (Layout "menu").
    • Click on the "New Game" button.
    • Open the browser console: The game saves and output the savefile every 1 sec in the console.
    • Notice that the section "collmemory" (near the bottom) stays empty.
    • Close the game (close the entire tab running the game).
    • Re-launch the game (Layout "menu").
    • Click on the "Load" button
    • Observe the browser console again: the "collmemory" section in the savefile gets bigger and bigger.

    Observed Result

    Memory leak in the savefile: the "collmemory" section keep expending.

    Expected Result

    No memory leak in the savefile: the "collmemory" section doesn't expend.

    Affected Browsers

    • Chrome: (YES)
    • Internet Explorer: (YES)

    Operating System and Service Pack

    Windows 8.1

    Construct 2 Version ID

    r206, 64bits

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Was able to reproduce in Chrome, didn't need to close the tab either, hitting refresh was enough. This only happens with the collision event, not with the "is overlapping" event.

  • In other words, it's exactly the same issue as this one:

    ...but it now requires the game to be relaunched (closing or refreshing the tab or using the "reload" button in the debugger) for the issue to happen.

  • Should be fixed in the next beta, thanks for the find.

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