7

When building my UWP in Release mode with .Net Native tool chain I have the Following error:

Error : ILT0005: nutc_driver.exe […] returned exit code -1073741819

There is no other error message whatsoever so I feel clueless to try and solve that problem. How can I gather information about the problem? What could it be and how to verify?

Notes:

  • Microsoft.NETCore.UniversalWindowsPlatform is on version 6.2.8
  • It builds fine in Debug mode with Net Native tool chain checked
  • I don't think it's an out of memory issue as I have <Use64BitCompiler>true</Use64BitCompiler> and the build agent has 14Gb of RAM
    • François
    • 3,164
    • 25
    • 58
    • If you comment the default runtime directive `` in the Default.rd.xml file under Properties and build it again, will the same issue occur? There is a [similar thread](https://github.com/dotnet/corert/issues/7408), you can check it. – Faywang - MSFT Nov 14 '19 at 09:21
    • Tks for the link. It says to add what you suggest when the app is too big (exit code 2) to ignore some code. I dont have exit code 2. – François Nov 14 '19 at 12:58
    • You can choose Tools->options->Projects and Solutions->Build Run, and change the **MSBuild project build output verbosity** and **MSBuild project build log file verbosity** to **Detailed**. Then build it again. You will receive more detailed information in Output, please provide the error information for us. If the error is too long, you can put them in a file and provide it. – Faywang - MSFT Nov 20 '19 at 05:18
    • I work on the .NET Native compiler. That exit code in HEX is (C000 0005) which maps to access violation. Would you be able to send me a repro? I can be reached at dotnetnative@microsoft.com. – MattWhilden Dec 10 '19 at 21:58
    • 1
      I have the same problem. Did you resolve this? – ED-209 Jul 02 '20 at 11:30
    • I stopped building with .net native. It builds in a few minutes rather than more than an hour. At the end no user saw any differences in terms of app performance so what's the point to use it? – François Jul 03 '20 at 21:02
    • 1
      Got the same error code, any news on the resolution? – Mike Jul 20 '22 at 06:04

    0 Answers0