问题描述
我们在实体框架代码中的测试机器上遇到了访问冲突.我想知道这是否可能是由于线程错误，或者更可能是由于硬件问题.
We've encountered an access violation on our test machine, in Entity Framework code. I'm wondering if this could potentially be due to a threading bug, or if it's more likely due to hardware issues.
这是一个部分调用堆栈:
Here is a partial call stack:
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Data.Common.Internal.Materialization.CoordinatorFactory`1..ctor(Int32 depth, Int32 stateSlot, Expression hasData, Expression setKeys, Expression checkKeys, CoordinatorFactory[] nestedCoordinators, Expression element, Expression elementWithErrorHandling, Expression initializeCollection, RecordStateFactory[] recordStateFactories)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeConstructor(IRuntimeMethodInfo method, Object[] args, SignatureStruct& signature, RuntimeType declaringType)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(Type type, Object[] args)
at System.Data.Common.Internal.Materialization.CoordinatorScratchpad.Compile()
这发生在我们在 IIS 7 (Server 2008 R2 SP1) 上的 ASP.NET 应用程序中，使用 Entity Framework 4 访问 SQL Server 2008 R2.我已经阅读了 EF 和 SQL Server 的访问冲突CE，但我们使用的是完整的 SQL Server.我们没有直接与应用程序中的任何本机代码交互 - 没有 P/Invoke 或 COM 互操作.
This happened in our ASP.NET app on IIS 7 (Server 2008 R2 SP1), using Entity Framework 4 to access SQL Server 2008 R2. I've read about access violations with EF and SQL Server CE, but we are using the full SQL Server. We aren't directly interacting with any native code from our app - no P/Invoke or COM interop.
这种情况只发生过一次.我个人认为这是机器的问题，而不是应用程序......机器之前已经蓝屏了几次.但我被要求将其作为一个可能的错误进行调查.
This has only happened once. Personally I think it's a problem with the machine, not the application... the machine has BSOD'd a couple times before. But I was asked to look into it as a possible bug.
如果它再次发生，我会考虑设置 DebugDiag 以捕捉它.有人有其他建议吗?
I'll look into setting up DebugDiag to catch this if it happens again. Does anyone have any other suggestions?
谢谢，
理查德
Thanks,
Richard
推荐答案
我想你可能是对的，我猜在同一个工作进程中运行了一些其他代码，导致一些内存损坏导致了这个错误.
I think you're probably right, I would guess that there was some other code running in the same worker process which caused some memory corruption that resulted in this error.
如果此工作进程中正在运行其他应用程序，您可能需要考虑将此应用程序分离到一个专用工作程序中.除此之外，我会将其归入让我们拭目以待"类别.
If there are other applications running in this worker process, you might want to look at separating this application out into a dedicated worker. Other than that I would put it into the "lets just keep an eye out" category.
这篇关于访问 SQL Server 的实体框架代码中的访问冲突的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！