Possible handle leak when repeatedly create/play/stop/dispose flyleaf players

[dev991301]

Possible handle leak when repeatedly create/play/stop/dispose flyleaf players

[arslan38]

+Up

[t3therdev]

we are also seeing memory leaks on our side. @SuRGeoNix

[SuRGeoNix]

I will review this in the weekend

[t3therdev]

hi @SuRGeoNix were you able to take a look into this?

[SuRGeoNix]

@dev991301 does this happen with trace log off? I cannot reproduce it so far (can you use the release's ffmpeg libraries?)

[dev991301]

@dev991301 does this happen with trace log off? I cannot reproduce it so far (can you use the release's ffmpeg libraries?)

@SuRGeoNix It does seem to happen with trace off. I am using the FFmpeg libraries that come from the Flyleaf 3.7.16 release. It also doesn't seem to matter if video acceleration is enabled or disabled.

In the Github code I submitted, would you be able to uncomment the other players in MainWindow.xaml and see what the handle count trend looks like?

[SuRGeoNix]

Here my results with 9 players:-

(Stable RAM/VRAM/GPU usage/Handles)

with Video Acceleration off

[t3therdev]

@SuRGeoNix did you leave it running for a long period of time?

[SuRGeoNix]

@t3therdev about 30'

[SuRGeoNix]

Guys, any news with this one? I couldn't reproduce it also in systems with different GPUs.

[dev991301]

I think the handle growth on my machines may be related to the version of the integrated Intel graphics drivers I am using. Running with an old version of a graphics driver the handles didn't grow (version 27.20.100.9079 which came from HP) but when upgraded to a newer Intel driver it did grow (version 31.0.101.5382). It also grew on a machine running Intel UHD graphics around version 31.0.x.x vintage. But it didn't grow when running off the NVIDIA graphics.

[SuRGeoNix]

Everything points to GPU / drivers so I'm not sure if there is anything left from Flyleaf side to fix. I had different issues with RX 580 and had to use older drivers to make it work properly. So I'm afraid I will close this as is not related to the library.

[SuRGeoNix]

Possible related WPF issue here dotnet/wpf/issues/7704

It would be interested to see if the problematic GPU/drivers having the same issue with WinForms.

Update: Seems that Config.Decoder.ZeroCopy = FlyleafLib.ZeroCopy.Enabled; could be a workaround.