{"action":"created","issue":{"url":"https://api.github.com/repos/tamasflamich/effort/issues/30","repository_url":"https://api.github.com/repos/tamasflamich/effort","labels_url":"https://api.github.com/repos/tamasflamich/effort/issues/30/labels{/name}","comments_url":"https://api.github.com/repos/tamasflamich/effort/issues/30/comments","events_url":"https://api.github.com/repos/tamasflamich/effort/issues/30/events","html_url":"https://github.com/tamasflamich/effort/issues/30","id":135732175,"number":30,"title":"AccessViolationException - Attempted to read or write protected memory","user":{"login":"hicks86","id":11144895,"avatar_url":"https://avatars.githubusercontent.com/u/11144895?v=3","gravatar_id":"","url":"https://api.github.com/users/hicks86","html_url":"https://github.com/hicks86","followers_url":"https://api.github.com/users/hicks86/followers","following_url":"https://api.github.com/users/hicks86/following{/other_user}","gists_url":"https://api.github.com/users/hicks86/gists{/gist_id}","starred_url":"https://api.github.com/users/hicks86/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hicks86/subscriptions","organizations_url":"https://api.github.com/users/hicks86/orgs","repos_url":"https://api.github.com/users/hicks86/repos","events_url":"https://api.github.com/users/hicks86/events{/privacy}","received_events_url":"https://api.github.com/users/hicks86/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2016-02-23T13:07:59Z","updated_at":"2016-05-19T20:49:55Z","closed_at":null,"body":"Hello,\r\nSo I am using the Effort.EF6 (1.1.4) and NMemory(1.1.2) framework for my Unit Tests - now I have only recently returned to using Effort after deciding it was probably the best route for my situation. I have been using the framework for the past month without an issue, until yesterday morning I came across an:\r\n\r\n> AccessViolationException was unhandled by user code\r\n> \r\n> An exception of type 'System.AccessViolationException' occurred in NMemory.dll but was not handled in user code\r\n> \r\n> Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.\r\n\r\n\r\nThe particular case I refer to seems to happen when trying to perform a LINQ Where(x => x.) on one of the properties of my DbContext. I will check my other unit tests to see if it is just querying that it occurs on.\r\n\r\nNow I have seen this issue before (https://effort.codeplex.com/discussions/632411) however it was never my laptop.\r\n\r\nAny ideas on what is causing this?? It is just strange that it reappeared yesterday."},"comment":{"url":"https://api.github.com/repos/tamasflamich/effort/issues/comments/220448041","html_url":"https://github.com/tamasflamich/effort/issues/30#issuecomment-220448041","issue_url":"https://api.github.com/repos/tamasflamich/effort/issues/30","id":220448041,"user":{"login":"kennethscott","id":823499,"avatar_url":"https://avatars.githubusercontent.com/u/823499?v=3","gravatar_id":"","url":"https://api.github.com/users/kennethscott","html_url":"https://github.com/kennethscott","followers_url":"https://api.github.com/users/kennethscott/followers","following_url":"https://api.github.com/users/kennethscott/following{/other_user}","gists_url":"https://api.github.com/users/kennethscott/gists{/gist_id}","starred_url":"https://api.github.com/users/kennethscott/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kennethscott/subscriptions","organizations_url":"https://api.github.com/users/kennethscott/orgs","repos_url":"https://api.github.com/users/kennethscott/repos","events_url":"https://api.github.com/users/kennethscott/events{/privacy}","received_events_url":"https://api.github.com/users/kennethscott/received_events","type":"User","site_admin":false},"created_at":"2016-05-19T20:49:55Z","updated_at":"2016-05-19T20:49:55Z","body":"Update-  Telerik sent me a corrected pre-release build of JustMock this morning to try.  I am very happy to report that it seems to be working in our initial testing.  Our unit tests seem to be working fine even with the Profiler enabled.  \r\n\r\nWe will continue testing with Telerik, but hopefully this is something they can include in their next release."}}