Application exit code: -1073741819

Application exit code: -1073741819

I am trying to run a "Detect Leaks" analysis on a large 64-bit windows application. Analysis starts as it should but stops almost immediately reporting: "No problems detected"

However, the collector messages reveals that the exit has happened in the middle of DLL loading, way before the business logic is started:


Analysis started...


Loaded module: C:\Windows\SYSTEM32\sechost.dll, address range [0x000007FEFEF30000-0x000007FEFEF4EFFF]

Loaded module: C:\Windows\system32\USP10.dll, address range [0x000007FEFEF50000-0x000007FEFF018FFF], minimal analysis

Loaded module: C:\Windows\system32\OLEAUT32.dll, address range [0x000007FEFF020000-0x000007FEFF0F6FFF]

Loaded module: C:\Windows\system32\GDI32.dll, address range [0x000007FEFF100000-0x000007FEFF166FFF], minimal analysis

Loaded module: C:\Windows\system32\msvcrt.dll, address range [0x000007FEFF190000-0x000007FEFF22EFFF], minimal analysis

Loaded module: C:\Windows\system32\RPCRT4.dll, address range [0x000007FEFF230000-0x000007FEFF35CFFF], minimal analysis

Application exit code: -1073741819

Result file: ...clip...

Analysis completed


A similar (?) problem was discussed in this forum earlier:

publicaciones de 9 / 0 nuevos
Último envío
Para obtener más información sobre las optimizaciones del compilador, consulte el aviso sobre la optimización.

...with Inspector XE 2013 Update 6 (build 283349)

This is hard to image what happened when running Inspector on your 64bit seemed to met 32bit DLLs for minimal analysis then crashed.

Can you please verify it in cmd?

1. Which is Visual Studio x64 Win64 Command Prompt - for example

2. "\Program Files (x86)\Intel\Inspector XE 2013\inspxe-vars.bat"

3. Run your app without Inspector

4. inspxe-cl -collect mi1 -- your-app

If the problem still persist on, you may find some clues from log file in result directory. For further investigating, you need to submit this issue with test case to Intel Premier.

Thanks, Peter 

You could try checking the box 'Enable interactive memory growth detection' before running the analysis.   This has a side effect of changing how the target application is instrumented, and it might be enough to avoid the problem.

As mentioned, without Inspector, application starts normally...

Inspxe-cl ... command seems to have the same behavior: " <message severity="verbose">Application exit code: -1073741819 </message>"

OTOH, checking "enable memory growth detection" and starting the analysis will cause the application to throw "System.BadImageFormatException: An attempt was made to load a program with an incorrect format. ..."

According to collector message app would still seem to be in the middle of loading DLLs.

I will file an issue.


>>...Application exit code: -1073741819

-1073741819 = C0000005 and this is a code for Access Violation exception.

It is possible that there is some internal problem with the application and as a result the Access Violation exception happens.

In this particular case I assume that the question is of something else, as the use of inspector more or less introduces the exception. And the exception comes in the DLL loading phase. Without Inspector in the  picture, the app starts as it should.

But of couse I can not be 100% sure. However, there have been somewhat similar cases discussed in this forum: and


>>>>...Application exit code: -1073741819
>>...In this particular case I assume that the question is of something else, as the use of inspector more or less
>>introduces the exception. And the exception comes in the DLL loading phase...

Output Window of Visual Studio shows all loaded DLLs and could you post a complete output?

You need to run your app under debugger and try to reproduce the issue(access violation exception).It is not clear which part of code generated that error.

Deje un comentario

Por favor inicie sesión para agregar un comentario. ¿No es socio? Únase ya