Build: Buildbox_3.1.3-3446.exe Branch: release Device/OS: Windows 10 pro 64-bit (10.0, build 17763) Frequency: 100% Steps to reproduce: Launch the Buildbox app and open Leap template While in 3D World map change the cube collision group to Enemy On Mind map connect Game Over output signal to 3D World "Load" node in order to create an infinite loop. Open Task manager on Processes tab and keep it in view Start the game and press on play button Observe Actual results: After few moments (1-2 minutes) you are able to see how your memory values for buildbox increases each time you "restart" or start a new game. Expected results: The game engine should clean the world and memory used should not increase on restart. Notes: This happens on both 3D and 2D worlds (2d worlds are a less impacted by this for some reason) The this.scene().restart() line of code has the same results and even if you use a game observer to redirect the user to the beginning of the world the result is the same. This is a major issue since this happens on android devices as well. You are playing the game and at some point the devices runs out of memory and the app crash generating a crash report. Video: Feel free to ask questions if something is unclear. cc: @TreySmith @Sean Buildbox @HueTheDev @NikRudenko
Thanks for the details, appreciate if you send this over to support@buildbox.com so that they investigate the issue and include in coming fixes
Has this issue been sorted out ? I am using 3.4.8 and I still face over memory consumption issue. Kindly enlighten on how to fix it.
