Memory leak in Info (EX9.Texture) or in FromSharedTexture (DX11)?!?

vvvv beta bug
1

quoted from DX9 to DX11 texture - #7 by kalle

hiho,
finally i also start messing around with that lovvvvely DX11-stuff…

currently lifting a quite heavy patch (4 videocams etc.) from DX9 to DX11.

i noticed a Memory leak within the module posted by joreg (have 6 instances in use…).

with level = 0 on the Info (EX9.Texture) the Shared Handle alternates each Frame (at least here).
Setting level to 1 after a few frames almost stops the leak; and hovering some output pins of the Info (EX9.Texture) seems to be finally very helpful…

your old kalle

p.s.: a modified version of the module is attached

DX9ToDX11 (DX11.Texture 2d).v4p (5.6 kB)

2

ai kalle,

the flickering of the sharedhandle comes from videotextures which are doublebuffered. so thats by design.

the Info node also has a Levels output. for videotextures that should be 1. is it? if so, changing the Level input really shouldn’t make any difference.

3

heyoreg,

from what i experience here the Level initially has to be 0.

if i just set Level Input to 1 i do not get anything what i would call a texture…

i confirm the Level Output being 1 but changing Level Input definetely makes a difference.
at least it does in my weighty patch.

and it definitely wants to leak Memory…

best regards