Related to #159 , it seems that some D3D8 applications will still make calls to SetVertexShader() after a Present call returns D3DERR_DEVICELOST and the device is lost. The Microsoft documentation mentioned in #155 seems to imply otherwise, but the Microsoft supplied d3d8dll seems to handle this case just fine so applications for DX8 probably just followed this behavior at the time. I am retaining the shader destruction on device release though, since in testing of d3d8.dll, shader objects don't increment the device refcount and this was causing d3d9 devices and shaders to leak under d3d8to9.
Related to #159 , it seems that some D3D8 applications will still make calls to SetVertexShader() after a Present call returns D3DERR_DEVICELOST and the device is lost. The Microsoft documentation mentioned in #155 seems to imply otherwise, but the Microsoft supplied d3d8dll seems to handle this case just fine so applications for DX8 probably just followed this behavior at the time. I am retaining the shader destruction on device release though, since in testing of d3d8.dll, shader objects don't increment the device refcount and this was causing d3d9 devices and shaders to leak under d3d8to9.