We’re seeing this problem on PVRVFrame (Win32) when we use client arrays that process committed CPU memory increases steadily at +2MB/sec without bound.
We do not see this same growth when running alternative emulators on Win32 (Mesa3D and ANGLE).
Are there any known PVRVFrame memory leaks with client arrays on Win32?
If not, could you regression test client arrays before cutting PowerVR SDK 3.5 to ensure that, if any are found, they will be fixed in 3.5?
If a PVRTrace capture would be useful, just let me know. Thanks!