COM接口修改突然开始导致异常

几年前，我继承了一个c#应用程序，它使用在非托管c++ DLL中定义的COM对象。从那以后，我一直在成功地调整对象接口，但在(可能无关的)VS2012升级之后，函数签名的添加和更改突然受到随机异常的惩罚，如ExecutionEngineException和SEHException。

我的理解是该应用程序使用免注册的COM。没有DLLRegisterServer实现，我也没有看到注册表中提到接口指南，只有c#中的一个…

[ComImport,
Guid("C2427CB1-D6AE-49e8-B266-114F981C3353"),
InterfaceType(ComInterfaceType.InterfaceIsIUnknown),
SuppressUnmanagedCodeSecurity()]
public interface IDC
{

和一个c++头文件

interface __declspec(uuid("C2427CB1-D6AE-49e8-B266-114F981C3353"))
IDC : IUnknown
{

为了确保，我决定在这两个地方交换一个新的向导，并发现它完全阻止了c#识别类:

System.InvalidCastException
Unable to cast COM object of type 'System.__ComObject' to interface type 'Apx.IDC'.
This operation failed because the QueryInterface call on the COM component for the
interface with IID '{the new guid}' failed due to the following error:
No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

(上面的错误显然是由混合公寓状态引起的，但是交换guid不会引起这个问题)。所以我推断一定有额外的相关细节在某处与我的更改相冲突。但它会在哪里呢?谢谢阅读…

编辑:

First-chance exception at 0x000007feec748be4 (clr.dll) in Apex.exe: 0xC0000005:
Access violation reading location 0xffffffffffffffff.
The Common Language Runtime cannot stop at this exception. Common causes include:
incorrect COM interop marshalling, and memory corruption. To investigate further,
using native-only debugging.
An unhandled exception of type 'System.ExecutionEngineException' occurred in Apex.exe

[PreserveSig] [return: MarshalAs(UnmanagedType.I1)]
bool LoadDisplayList(IntPtr fileHandle, IntPtr pDisplayList,
UInt16 version, IntPtr pComparison);

和

virtual bool __stdcall LoadDisplayList(HANDLE fileHandle, class CDisplayList * pDisplayList,
WORD version, CDisplayList * pComparison) = 0;

以 结尾的堆栈跟踪

[Native to Managed Transition]  
Apex.Graphics64.dll!CDisplayList::LoadRenderRecs(void * f=0x000000000000056c, CDisplayList * pComparison=0x0000000023ad2cf0)  Line 1772 C++
Apex.Graphics64.dll!CDisplayList::Load(void * f=0x000000000000056c, unsigned short version=0x0002, CDisplayList * pComparison=0x0000000023ad2cf0)  Line 1845 + 0x26 bytes   C++
Apex.Graphics64.dll!CBaseDC::LoadDisplayList(void * f=0x000000000000056c, CDisplayList * pList=0x0000000023ad2cf0, unsigned short version=0x0002, CDisplayList * pComparison=0x0000000023ad2cf0)  Line 1896 + 0x33 bytes    C++
[Managed to Native Transition]  
Apex.exe!Apex.DDC.LoadDisplayList(System.IO.FileStream file = {System.IO.FileStream}, Apex.DisplayList displayList = {Apex.DisplayList}, ushort version = 0x0002, Apex.DisplayList comparison = null) Line 1124 + 0xaf bytes    C#
Apex.exe!Apex.DisplayList.Load(System.IO.FileStream f = {System.IO.FileStream}, ushort loadVersion = 0x0002, Apex.INode stubsRoot = {Apex.ViewPort3D}, Apex.DisplayList comparison = null) Line 166 + 0x53 bytes    C#

确切的崩溃点有所不同-这里它实际上设法进入LoadDisplayList()，这比通常要好。由于崩溃表明堆损坏，我尝试将函数的签名剥离为无参数的void返回，将其内容减少为跟踪，并在对象创建后立即调用它-仍然会导致崩溃。如果我将相同的函数移动到定义的顶部，它不会崩溃，在这种情况下，一些其他接口函数崩溃，导致我认为它更有可能是COM问题，而不是算法级内存损坏。