Open GoogleCodeExporter opened 9 years ago
Note this was with a series of patches -- I'll run it again shortly with ToT
and see if that isn't a false alarm.
Original comment by jmad...@chromium.org
on 5 Jun 2014 at 6:19
It seems the CopySubresourceRegion error was crashing older nVidia drives,
though new ones are more robust. See issue chromium:384420. The error is during
native buffer storage resize data copy step using the new large size instead of
the old smaller size.
Also we are triggering D3D11 errors in the gl-pointcoord test and we should
investigate those.
Original comment by jmad...@chromium.org
on 16 Jun 2014 at 5:18
Original comment by jmad...@chromium.org
on 16 Jun 2014 at 5:18
https://chromium-review.googlesource.com/#/c/203776
Original comment by jmad...@chromium.org
on 16 Jun 2014 at 5:21
https://chromium-review.googlesource.com/#/c/203778/
Original comment by jmad...@chromium.org
on 23 Jun 2014 at 2:58
Just picked up these from angle_tests:
D3D11 WARNING: ID3D11DeviceContext::DrawIndexed: Vertex Buffer at the input
vertex slot 0 is not big enough for what the Draw*() call expects to traverse.
This is OK, as reading off the end of the Buffer is defined to return 0.
However the developer probably did not intend to make use of this behavior. [
EXECUTION WARNING #356: DEVICE_DRAW_VERTEX_BUFFER_TOO_SMALL]
D3D11 ERROR: ID3D11DeviceContext::Map: This resource is already mapped! [
RESOURCE_MANIPULATION ERROR #2097213: RESOURCE_MAP_ALREADYMAPPED]
D3D11 ERROR: ID3D11DeviceContext::CopySubresourceRegion: Cannot invoke
CopySubresourceRegion while a Subresource of the source is mapped.Source
subresource (0) is mapped. [ RESOURCE_MANIPULATION ERROR #283:
COPYSUBRESOURCEREGION_INVALIDSOURCESTATE]
Looks like some of them are from the PBO/ReadPixels tests.
Original comment by jmad...@chromium.org
on 12 Sep 2014 at 8:25
Original issue reported on code.google.com by
jmad...@chromium.org
on 5 Jun 2014 at 6:17