CODEWITHSUNDEEP
visual-studio-2015uwp.net-nativevisual-studio-2017
Gaz83
Gaz83

Reputation: 2865

Error Creating UWP store package or Release Build - Out of Memory

Want to submit my app to the windows store but I am getting compile errors. If I try to create a Release Build or if i try Create App Packages of my app I eventually get the following.

ILT0005: 'C:\Program Files (x86)\MSBuild\Microsoft.NetNative\x86\ilc\Tools\nutc_driver.exe @"C:\Users\garet\documents\visual studio 2015\Projects\TestUwpProject\TestUwpProject\obj\x86\Release\ilc\intermediate\MDIL\TestUwpProject.rsp"' returned exit code 1

Out of Memory

Things I have tried.

Note:- my laptop I tried it on is running VS2017 RC and the latest insider preview of windows 10.

The only thing i can note is that if I create a blank project and add all the nuget packages etc it compiles fine which seem to mean an issue with my code but I wouldn't know where to start.

Issue looks similar to this but I am not using EF.

Out of memory error when compiling UWP app in release mode with .Net native

Upvotes: 1

Views: 762

Answers (1)

MattWhilden
MattWhilden

Reputation: 1696

Sorry to hear it's causing you trouble. It's a bit difficult to diagnose without more information but it's most likely that one of our “whole program” analysis phases has exploded exponentially in memory. The most common frameworks that we see this happen with are EF and the Syncfusion libraries. Working around the bug will depend on the specifics of your program but hopefully a bit of twiddling will get you back on your feel.

The easiest thing to attempt is to try to remove dlls that you're not actually dependent on. Fewer libraries in, fewer things to have the compiler think about. This is particularly useful for the Syncfusion libraries as their entire stack is in one Nuget package but most folks only use a small slice of the functionality there.

If that's not successful, you can get help from us more directly by sending a mail to [email protected]. Please send along an ILCRepro file as it's the fastest way for us to help out.

We’ve made progress correcting some of these issues but some of the confounding factors require architectural level changes to the compiler that are still ~1 year out.

Disclaimer: I work on the .NET Native compiler+runtime team.

Upvotes: 1

Related Questions