[CONNECT] - Microstation has stopped working

salvatore montella said:

I have developed an AddIn, in c #, for Microstation Connect version 1

Have you tried using Viz Studio's debug tools?

Hi Salvio,

You likely will need to crash again setting MS_MINIDUMPTYPE=7.

Can you provide the current memory dump until a full memory dump can be zipped and posted?
Line 863: Wrote a mini-dump type 0x4 to "C:\TEMP\Bentley\MicroStation\10.0.0\MiniDump.dmp".

Thank you,
Bob

Hi Robert, the minidump is in attachment 

Thank you,

SalvioMiniDump.rar

Hi Salvatore,

based on the file size, I guess it's not "type 7" minidump (but maybe I am wrong ;-).

It think when MS_MINIDUMPTYPE=7 is set, the full dump should be created, which I assume will produce much bigger file. Also, because NET application is involved, you should also configure to include Page Heap also. See this wiki article how to do it.

With regards,

  Jan

Hi Salvatore,

I am not "exception analyses start" ;-) so the only things I was able to understand from provided mini dump using (great) WinDbg Preview application (available in Microsoft Store for free, or older version in every Visual Studio / Windows SDK installation) is that the crash is caused by access violation exception in PowerPlatform dll.

It's hard to guess where the problem can be. To create full dump including heap can provide some extra information. You also did not share ExceptionLog, which also contains useful information.

What I remember, these issue can be cause by:

• Wrong code, like to pass not valid anymore instance (e.g. element removed from design file in a meantime) to some method, which ends with exception (invalid memory, wrong pointer...) deep inside PowerPlatform engine.
  Without knowing your code, how it's structured and what classes are used, it's hard to guess. I recommend to check whether all IDisposable objects are properly disposed as soon as possible etc.
• In some cases it can be caused also by corrupted DGN file (but it can be tested that application works fine with other files).

BTW Did you try to debug running MicroStation process from Visual Studio? When "catch all exceptions" is used, it should show where is the source of invalid API call (at least is should be in call stack list).

With regards,

  Jan

Also, can you share small add-in c# project to simulate this issue at our end? 

In attachments other minidump 

ExceptionHistory.zip

Hi Salvatore,

salvatore montella said:

In attachments other minidump 

I am afraid that until better memory dump is provided, nothing investigated.

In my earlier answer I provided link to wiki with description how to create full memory dump, including managed heap.

Because you mentioned you developed C# addin, so I assume you are developer. Based on that I think it's clear it's not possible to analyze C# addin crash, when the provided data is only minidump without MicroStation page heap.

It's written clearly in the wiki:

To trouble shoot Managed Exception from .NET and Heap corruptions, 
we would require a Type 7 (Full Dump) with Page Heap.

Regards,

  Jan

Hi salvatore montella,

1. Can you please set MS_MINIDUMPTYPE=7 at the OS System environment variables; necessary for .NET exceptions to produce a full memory dump; then rename/disable the variable after creation of a full memory dump file?  For more details on how to set the variable and collect exception history logs, please see: Generate Type-7 minimdump files.
   
   
2. Can you provide a test case that development has requested?

Both these items are essential to provide to identify what is going wrong in your code and provide recommendations to fix the problem(s).

Thank you in advance,
Bob