Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory Leakage #466

Closed
cxgym opened this issue May 19, 2024 · 11 comments
Closed

Memory Leakage #466

cxgym opened this issue May 19, 2024 · 11 comments

Comments

@cxgym
Copy link

cxgym commented May 19, 2024

【v3.7.48】Opening multiple streams in the same application results in a continuous increase in memory until the program crashes, log is not have error, but Opening single streams it is no problem.

@SuRGeoNix
Copy link
Owner

Once again @cxgym by trying to describe an issue with 1 line and expecting me to understand it and fix it makes no sense.

@cxgym
Copy link
Author

cxgym commented May 20, 2024

I can only describe the problem I encountered because there is no valuable reference in the logs. Opening multiple streams in an application is normal if software is used to decode it. If I enable D3D hardware acceleration, it will run normally on some machines, while running on another machine will cause memory leakage. However, opening only one stream is not a problem

@cxgym
Copy link
Author

cxgym commented May 20, 2024

520

@cxgym
Copy link
Author

cxgym commented May 20, 2024

I suspect there is a thread safety issue here

@cxgym
Copy link
Author

cxgym commented May 20, 2024

Hope to give me tips, thanks.

@SuRGeoNix
Copy link
Owner

Check this #450 and this #448

@cxgym
Copy link
Author

cxgym commented May 21, 2024

Is it because of a problem with the gpu driver?

@cxgym
Copy link
Author

cxgym commented May 21, 2024

GPU 0
Intel(R) Iris(R) Xe Graphics
Drive Version: 31.0.101.4953
Drive Date: 2023/11/7
DirectX Version: 12 (FL 12.1)
it is memory leakage

GPU 1
Intel(R) Iris(R) Xe Graphics
Drive Version: 27.20.100.8984
Drive Date: 2020/11/19
DirectX Version: 12 (FL 12.1)
it is right

@SuRGeoNix
Copy link
Owner

From what other users said in the past is seems that is related with intel integrated graphics. Not sure if that's intel's issue or the combination of Intel/WPF. I was not able to reproduce it myself yet.

@cxgym
Copy link
Author

cxgym commented May 28, 2024

Config.Decoder.ZeroCopy = FlyleafLib.ZeroCopy.Enabled;
It can indeed solve my problem. but it will affect other functions?

@SuRGeoNix
Copy link
Owner

Thanks interesting. The only problem by forcing ZeroCopy it would be that you will have visible codec's padding pixels at the sides. (eg. full row of green pixels at the bottom of the frame). By checking the source code it seems that intel driver has the issue with the CopySubresourceRegion. Another open intel issue possible related is this https://community.intel.com/t5/Developing-Games-on-Intel/Memory-leaks-on-Intel-Iris-Xe-graphics/td-p/1585566

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants