Can you think of any reason why would Context3D.clear take so much time to complete. It almost takes as much time as whole Box2D physics simulation (with a lot of objects and joints) which is really crazy and definitively should not happen. This is not happening on Desktop only on iOS and Android.
I have tested this on iPhone 7 Plus. I have also tested on iPhone X but it seams that iPhone X is too fast to be affected by this. I have also tested on Samsung Galaxy s9 with exynos processor which should have very similar performance as iPhone 7 plus and it works so much better on Samsung because
I can only assume on Samsung Context3D.clear it does not take so much time to complete. I do not have Scout profile of Samsung s9 because I have tested in on Store. So it looks like iOS is affected way more.
Here is the Adobe Scout profile screenshot:
And here is the Adobe Scout profile file:
In Adobe Scout profile select frames 16,804 - 23,489. It is about of 1 minute of game play. During that time no display or physics objects where crated (you can see that in Memory Allocations tab).
This looks like it is Adobe AIR Bug. Should we create ticket for this. What are your thoughts?
This has serious performance implications for iOS and Android and on devices where my game should work perfectly this is destroying it. And it is just a Context3D.clear method which is stupid really.
I am using latest Starling and AIR 30 Beta. This is also happening with AIR 29.