Fix optix7 bug causing access violations #28
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
in
void RenderCore::SetMaterials( CoreMaterial* mat, const int materialCount )
underRenderCore_Optix7
, thehostMaterialBuffer
is initialized with sizematerialCount
, butmaterialBuffer
has sizematerialCount
and attributeON_DEVICE
set.This triggers
if (location & ON_DEVICE) CopyToDevice();
and eventually performs memcpy with size(materialCount + 512) * sizeof(CUDAMaterial)
, which can occationally trigger access violation during tinyapp startup.Thanks for the project, and please see if this patch helps.