Memory leak related to camera processing about letsrobot-android

[SkyeOfBreeze]

Starting to investigate

[SkyeOfBreeze]

Memory leak is occurring in this function:
https://github.com/btelman96/runmyrobot_android/blob/8c74fda00181842f581e19b9fc0ada7220665aec/letsrobotandroid-api/src/main/java/tv/letsrobot/android/api/components/camera/CameraBaseComponent.kt#L134-L139

If the network is really bad, this will just keep on building up. Fix would be to add an external Queue mechanism

[SkyeOfBreeze]

Moto Z Profiling data

[SkyeOfBreeze]

This appears to be a mix of Bitmap leaking and handler freezing

[SkyeOfBreeze]

332bcd5 only fixes leaking issues with camera2. The main leak still exists

Edit: This actually broke camera and was reverted

[SkyeOfBreeze]

How this happened:

Frames are sent to an android handler. If the phone cannot process data fast enough or the network is too slow for given bitrate, objects will start to pool up. each time a frame is processed, the pool is eliminated, but if it goes too long without sending a frame, it builds up to the point where the app crashes.

This now will not queue data to the handler unless the handler has no data at all

[SkyeOfBreeze]

Moto Z profiling. 1920x1080 at 10Mbps, which was really laggy. Saw no bad memory spikes

Spike at the beginning is the profiler initializing