Kevin Gosse • 11/25/2020

AccessViolation in ObjectNative::IsLockHeld (part 2 of 2)

Read Original

This technical article details part two of an investigation into random application crashes caused by an AccessViolationException in the CLR's ObjectNative::IsLockHeld method. The author analyzes memory dumps and assembly code to trace the issue to orphaned locks in an Orchard CMS output cache filter, explaining the threading problem within the ASP.NET MVC event lifecycle.

0 comments
#debugging #Net Framework #Memory Dump
AccessViolation in ObjectNative::IsLockHeld (part 2 of 2)

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 4 votes
2
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
3
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
4
Quoting Thariq Shihipar
Simon Willison • 1 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes