While making use of the EGL debug context support in PVRVFrame 10.1 (in PowerVR SDK 3.5), I noticed that there was persistent memory growth of ~40MB/sec.
I tracked it down to calling glDebugMessageInsertKHR() in an EGL debug context under PVRVFrame 10.1 (for reference, see KHR_debug). That is, inserting debug markers in the GL object stream under the PowerVR GLES emulator was the cause of the growth. When an EGL debug context is enabled, I call this many times per frame.
Could you please look into this leak and fix it in the next release of PVRVFrame? Debug markers are useful in PVRTrace to cross-correlate GL call sequences with actual code. If you’d like an example .pvrt file with these markers in it, let me know and I’ll upload one
(BTW, I should note: merely creating an EGL debug context and possibly calling glObjectLabelKHR() to assign English-descriptions to OpenGL object handles did not appear to cause persistent memory growth. That’s not too surprising because these don’t involve calls which are made every frame.)