Unity memory leak when retrieving images

[mpalau]

Hello everyone,

For our current project in my company we decided to use Leap Motion in order to get Infra Red images and analyze data with them, we have achieved our goals and the detection works perfectly fine, the problem comes from the requirement for obtaining those images.

In order to recieve images we must:

1. Subscribe to the event Images ready ->
   controller.ImageReady += OnImageReady;

2. Set the correct policy ->
   controller.SetPolicy(Controller.PolicyFlag.POLICY_IMAGES);

On activating the policy, the memory leak begins, no other data affects this result. Removing this line provokes the memory leak to disappear but the images will not arrive.

This code has been isolated and memory is rising more than 2 GB per minute.

We would really appreciate if someone can tell us where we are wrong or how to correct this!

[jselstad]

If you run any of the base VR passthrough scenes in the Core asset examples, do you get a memory leak?

The line you’re disabling of course turns off receiving the images, but I doubt it’s what is responsible for the memory leak.

It sounds like you could be leaking textures or materials (accidentally creating a new instance of them every frame rather than “Release()”ing them when necessary).

[mpalau]

Thanks to the Core examples, we could retrieve the images without the leak, we used the event from the infrared example and from that event called our code. Now everything runs smoothly.

Just for adding information, this code is provoking the leak:

using UnityEngine;
using Leap.Unity;
using Leap;

public class LeapImageBase : MonoBehaviour
{
    Controller controller;
    LeapServiceProvider provider;

    private void Awake()
{
    provider = GetComponent<LeapServiceProvider>();
    if (provider == null)
        provider = GetComponentInChildren<LeapServiceProvider>();
    if (provider != null)
    {
        controller = provider.GetLeapController();
        controller.SetPolicy(Controller.PolicyFlag.POLICY_IMAGES);
    }
}
}

This script alone is provoking the leak for us, with an empty scene just with the provider in the same GameObject.