Camera control 'memory leak' and workaround

[PaulD1]

In our tests, in the Android Player (have not tried iOS), using the camera control with a StreamRate other than 0 results in the storage used by the App gradually increasing to about 2Gb - a video stream from the 'view finder' is stored on the device. It does not seem to matter how long the StreamRate is set for (we usually use 100 as this recommended in the documentation), Power Apps just continues to capture and store the video stream for as long as the camera control is active. This appears to cause some performance slow-downs on lower spec devices without lots of storage to spare.

To overcome this, you can set the StreamRate to 0, but note:

• You will no longer be able to capture a photo using Camera.Stream, instead you must use Camera.Photo
• Camera.Photo is only supported in the OnSelect of the Camera control itself (if you put it on a separate button, it will not capture a photo)
• If you turn on the setting for 'Enhance Media Capture', which greatly improves performance of using SaveData/LoadData with images (which is glacial), then the OnSelect event of the Camera will not fire in Studio (making testing pretty tough) but it does work on the Android Player (have not tested other platforms as not relevant to our scenario).

Hope the above info is helpful and saves others the many hours of investigation we had to carry out to establish the nature of the bug and workarounds.

[timl]

Thanks for sharing this @PaulD1.  Whilst this is something that I have not encountered, I hope that this is something that Microsoft fixes.