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

Huge memory leak on wglDXLockObjectsNV/wglDXUnlockObjectsNV when a texture retrieving. #3

Closed
black-sire opened this issue Aug 7, 2014 · 4 comments

Comments

@black-sire
Copy link

Has anyone encountered this problem?
In my case it is observed on GTX 880M with latest drivers.

@leadedge
Copy link
Owner

leadedge commented Aug 8, 2014

Yes this is a bug in the NVIDIA driver. It does not always appear. In my case, I cannot see it with Windows process monitor or with leak checking. But for some systems there is a huge leak as you have discovered.

Malcolm Bechard has been communicating with NVIDIA and it appears that they have fixed the problem and a driver with the bug fixed may be released very soon.

Meanwhile we cannot use DirectX 11 for the GL/DX interop functions apart from testing, and that is why I restored the option for DirectX 9 within the SDK. By using "SetDX9(true)" within your app, all the interop functions will use DirectX 9 instead of DirectX 11 and the app will be 100% compatible with existing Spout apps.

@Kj1
Copy link

Kj1 commented Dec 6, 2014

Had the same issue with drivers from end 2013, but updating the nvidia drivers fixed it.

@elliotwoods
Copy link

So this isn't an issue with latest NVidia drivers? if so then close the issue?

@leadedge
Copy link
Owner

OK.

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

4 participants