[quote:rdlyqaic]This kind of report is really confusing. I could probably fix two other bugs in the time it just takes to read this much information, watch the videos, and figure out exactly which problem you're talking about
Hmm confused? the thread Points to "High Cpu" across the whole page like 100 times, and if you go straight to the "Observed "Result" & "Expected Result" It gives the short version of the Problem
Technically the videos it was to help you to avoid ("read this much information")
Anyway thanks for checking it
[quote:rdlyqaic](since it appears to have changed at some point during this thread).
Nothing at all has been changed on this thread just the Title from "App Memory Leak" to "High CPU (App) In All The iphones"
Thread started with a
Capx and Video of >>Coccon Canvas+ : >>>but since is not supported anymore and you asked if the problem happens in different platforms then the Thread ended up with a
Video of >>> PhoneGap: showing the "High Cpu" swell
[quote:rdlyqaic]Can you file a new bug and basically try to keep it as concise as possible? Stick to officially supported platforms only, a minimal repro project, clear steps to follow, and the expected and observed result.
Sure no problem I will make sure is short the next Time, I apologize
[quote:rdlyqaic]I'd point out that the CPU usage in Construct is a timer-based estimate. It's not very accurate for mobile devices because of the way they throttle to save power. I investigated another "high CPU" iOS bug and it just turned out to be this. In maximum performance mode, it might be using something like 9% CPU - hardly any. However if the OS determines it's not that busy, it might throttle down the CPU to be 10x slower, in order to save battery life. However now a timer-based CPU usage measurement indicates 90% CPU! That's a misleading number. Due to this power throttling, you can see a counter-intuitive effect where as you create more objects and add more CPU work, the measured CPU usage actually drops as it kicks up in to a higher performance mode and completes the same work quicker.
Cool Thanks very much for your explanation, I got now a good understanding on how Construct works, I thought (timer-based estimate. It's not very accurate) it applied to when we test projects over Wifi only
so it looks like this is not the case then, Even exported Capx and installed on the phones there is no way to test the real performance within Construct, I understand now
[quote:rdlyqaic]So I'd guess any "high CPU on mobile" bugs probably just come down to this. It'd be best to use another app to measure the real CPU usage on the system if possible.
Thanks for the suggestion I will try that
Since "Construct is a timer-based estimate. It's not very accurate for mobile devices" then I think you can close this bug as there is nothing more we can discuss at the moment, I will have to look with different "Cpu Checker" and if I find anything I will open a new bug like you said
Thanks very much for your Time