Skip to content

fixing AccessViolationException on ReadMetadataHeader#24464

Merged
ivanbasov merged 2 commits intodotnet:dev15.6.xfrom
ivanbasov:dkm
Feb 2, 2018
Merged

fixing AccessViolationException on ReadMetadataHeader#24464
ivanbasov merged 2 commits intodotnet:dev15.6.xfrom
ivanbasov:dkm

Conversation

@ivanbasov
Copy link
Contributor

Customer scenario

The user debugging process crashed during the execution

block = GetMetadataBlock(previousMetadataBlocks, index, ptr, size);
in the debugger. The pointer created just above
ptr = module.GetMetaDataBytesPtr(out size);
points to a bad block.

The debugger crashes with
CLR_EXCEPTION_System.AccessViolationException_80004003_System.Reflection.Metadata.dll!System.Reflection.Metadata.MetadataReader.ReadMetadataHeader

Bugs this fixes

VSO 187805

Workarounds, if any

No

Risk

Low

Performance impact

No

Is this a regression from a previous update?

No

Root cause analysis

This happens on the edge between Roslyn, Visual Studio and user debugging processes. There are various interactions between processes with different timings. Not all of them were considered.

How was the bug found?

Watson

@ivanbasov
Copy link
Contributor Author

Tagging @r-ramesh for review

@jinujoseph
Copy link
Contributor

pending barcheck approval for 15.6

@natidea
Copy link
Contributor

natidea commented Feb 2, 2018

N.B. This is currently targeting dev15.7.x, but is submitted for 15.6

@jinujoseph
Copy link
Contributor

@ivanbasov approved to merge via link can you retarget to 15.6 branch pls

@ivanbasov ivanbasov changed the base branch from dev15.7.x to dev15.6.x February 2, 2018 18:50
@ivanbasov ivanbasov merged commit 07eb95d into dotnet:dev15.6.x Feb 2, 2018
@ivanbasov ivanbasov deleted the dkm branch February 2, 2018 20:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants