Open GoogleCodeExporter opened 9 years ago
So stuff's moved around considerably since this was filed, but it looks like we
still only check for OUTOFMEMORY errors on CreateRenderTarget(View) calls in
both DX9 and DX11.
We should probably either add the INVALIDARG/INVALIDCALL case, or be doing
checks against the max supported render target dimensions before they reach
CreateRenderTarget. That D3D is returning INVALID errors on these calls implies
that they expect us not to pass out-of-caps values here. (Would be interesting
to determine whether the response differs between DX9 and DX11.)
(Semi-relatedly-- it looks like we don't even check for OOM conditions after
render target creation in the swap chain classes. It might be prudent to add
checks there.)
Original comment by shannonw...@chromium.org
on 29 Jan 2015 at 11:18
Original issue reported on code.google.com by
jda...@gmail.com
on 6 Aug 2014 at 1:07