I am re-opening this issue because your answer was completely inaccurate and incorrect.
You replied: "The snapshot you sent me on Twitter (note: it's more useful to keep it in the bug report itself)". That is wrong. I never sent you anything on twitter. I attached the screenshots of the memory leak directly to this bug report. I have no idea what you are referring to.
You replied: "screenshot only indicates 179mb usage". That is wrong. Again. The screenshots attached to my ticket clearly show the memory leak over time going up as high as 356mb after 90 minutes. Here it is again:
You said: "If you want to send a more useful snapshot, export again with "minify script" off, since the minify option has made the majority of the snapshot unreadable". That is wrong (yet again). The screenshots (and the issue) was observed without minify script enabled.
I may be willing to accept that it is with Windows Phone 8.1 code, as it is after all still in beta, but the fact that you are talking about things I am completely unaware of (such as sending you minified code on Twitter) leads me to believe that you are either mistaken, or are responding to a completely wrong ticket. Furthermore, I have tested by running other WP8.1 apps (not from Construct 2) and they successfully run for over 8 hours without crashing.
I am a Windows Phone user, and the main reason I chose to create my app with your tool was for Windows Phone support. Prove to me that this is not a bug, or refund my money. Your choice.
Over time, a project exported as a Universal 8.1 (Windows 8.1 and Windows Phone 8.1) app from Construct 2 r168 will leak memory only in Windows Phone 8.1. Despite sharing the same code, the Windows 8.1 build does not leak memory. Only the Windows Phone build does.
Attach a Capx
This issue was observed with my own capx as well as your own template files. No need to appach a capx file... simply use the Flapping Bird template with no modifications. I tested and confirmed the same issue occurs.
Description of Capx
Test with Flapping Bird template.
Steps to Reproduce Bug
- Export app from Construct 2 as Universal 8.1.
- Open the project in Visual Studio 2013 with Update 2 RC.
- Ensure you are are the Windows Phone app
- Do nothing. The app immediately starts leaking memory, even just sitting on the main play screen. The memory number keeps going up. It never drops back down.
- Try with Windows 8 and notice there is no memory leak.
The app slowly increases total memory used, about 1-2 MBs per minute. Eventually, app crashes as it runs out of memory.
I expect the memory use to remain the same over time.
Windows Phone 8.1 Only.
Operating System and Service Pack
Windows Phone 8.1 (issue occurs on device with Lumia 920, and in emulator)
Construct 2 Version ID
Construct 2 release 168 64bit