HoloLens 2 - Encoder stops after 90 frames + possible memory leak?

[dgblack]

Hi, thanks for the great library! I'm having a bit of an odd issue on a HoloLens 2 (Unity, UWP, ARM, latest release of PopH264). I'm pushing frames whenever one becomes available from the camera, and every time I push a frame, I increment a frameCounter. In Unity's Update function, I call:

var FrameMaybe = Encoder.PopFrame();
if (FrameMaybe is PopH264.H264Frame Frame)
{
    Debug.Log($"Success. Frame counter {frameCounter}");
    await Task.Run(() => { callback(Frame.H264Data); });
}
else
    Debug.Log($"Failed. Frame counter {frameCounter}");
FrameMaybe = null;

It consistently gets up to frameCounter = 90 with success on every frame, and then fails for the rest of the execution.

I can circumvent the issue by having two encoders, and every time the count almost reaches 90, I switch to the other one and dispose of the first, then switch back and dispose of the second, etc. This seems inefficient and unnecessary though. Any idea how to fix the actual problem?

Additionally, I monitored the memory usage while running this, and it creeps up pretty quickly. As soon as I stop encoding the frames, it stops increasing. Is it possible that there's a memory leak in the encoder somewhere? I'm not using Texture2Ds or anything that would cause the memory increase on the Unity side.

Edit: I kept all the code but commented out the push, and the memory leak disappeared, so nothing before the encoder is causing the leak. I then kept everything but after popping didn't do anything with the frame, and the memory leak persisted, so nothing after the encoder is causing the leak either. Really seems like it's inside the PopH264 library.

Thank you!
David

[dgblack]

One thing I noticed is that when I print the frame metadata, the OutputQueueCount value corresponds with my frameCounter value. Shouldn't the output queue size remain constant if I'm popping the frames at (at least) the same rate as I'm pushing them? Also, does destroying the encoder clear its frame queue? It doesn't seem to free any memory when I dispose of the encoder in C#.

[dgblack]

Ok, I fixed part of the second comment. Whenever I push a frame, I have to pop twice. First, I get a packet with DataSize of 6, and then I get the main packet with DataSize of several thousand. Do you know what the 6 bytes are for? Anyway, now the OutputQueueCount remains steady, but the memory leak and the 90 frame problem are not fixed.