Hi,
I've got the Mali Debugger hooked up and am trying to profile my app, the issue is that MGD doesn't appear to recognise the end of the frame, which means that a capture also fails (or runs indefinitely). This is from a Unity GLES app. You can see from the screenshot that a single frame contains all the GLES calls once the application has started. Is this a configuration issue of any kind?
Thanks in advance.
Hi newcomma,
Is it possible to get a reproducer app from you so we can begin investigation?
Also sending us the MGD capture could also be useful in our investigation.
Can I ask, are you attempting to do any VR rendering in your app?
Kind Regards,
Michael McGeagh
Hi Chris,
Thanks for responding. This is from a Unity project (4.6.4) so I'm actually unsure what API call signals are being used by the renderer under the hood, I don't know if you guys have any insight into this?
This is probably because there are no calls to eglSwapBuffers present in the trace from frame 4 onwards, could you confirm that? Could you also let us know exactly how you are finishing a frame? i.e. what API call signals the end of a frame and the start of a new one.
Thanks,
Chris