Note: this only happens with the utility functions.

Thanks for the report. This is a bad one, basically the API is broken.

We can fix it easily in the Java case. Instead of a single long we should return two (the two pointers) and have the Java layer perform the additional destroy as needed.

@romainguy I don't think it will work, because the java (kotlin actually) layer doesn't store the long, it just returns it to the caller:

    fun createIndirectLight(engine: Engine, buffer: Buffer, options: Options = Options()): IndirectLight {
        val nativeEngine = engine.nativeObject
        val nativeIndirectLight = nCreateIndirectLight(nativeEngine, buffer, buffer.remaining(), options.srgb)
        return IndirectLight(nativeIndirectLight)
    }

This is completely stateless.

We can store that in the Java IndirectLight object. It's very doable.

Okay but we now made all the Java objects bigger just to support that broken API -- And we're breaking the model of java objects being "dumb", now these have logic.

circling back after two years. I think we can just make createIndirectLight return a pair of IndirectLight and Texture. Callers will have to own the Texture as well.