From: Ken Thomases Subject: wined3d: Don't clear the GL context such that it can't be restored. Message-Id: <1CDD6D76-E670-4BC9-9234-1311DE6A8314@codeweavers.com> Date: Wed, 5 Feb 2014 14:01:15 -0600 The original author of the code being removed, Matteo Bruni, gives his blessing to removing it. If the driver bugs mentioned in the comment resurface, we can look into working around them in a different way that doesn't break other stuff (and documents the problems more clearly). Fixes . --- dlls/wined3d/device.c | 3 --- 1 files changed, 0 insertions(+), 3 deletions(-) diff --git a/dlls/wined3d/device.c b/dlls/wined3d/device.c index 256052f..4cd6342 100644 --- a/dlls/wined3d/device.c +++ b/dlls/wined3d/device.c @@ -1016,9 +1016,6 @@ HRESULT CDECL wined3d_device_uninit_3d(struct wined3d_device *device) if (!device->d3d_initialized) return WINED3DERR_INVALIDCALL; - /* Force making the context current again, to verify it is still valid - * (workaround for broken drivers) */ - context_set_current(NULL); /* I don't think that the interface guarantees that the device is destroyed from the same thread * it was created. Thus make sure a context is active for the glDelete* calls */