Application internal exception in Windows.UI.Xaml.dll

Question

I am working on the Windows 10 Store of Windows Universal using the Visual Studio 2015, C # and XAML community. It unpacks the compressed file and displays the images found in it.

The line contains 0 warnings.

The debug version works fine regardless of the size of the input file.

The release version works great with typical input file sizes.

For large input files (~ 100 1 megapixel images), the release assembly sequentially worked with "Unhandled exception in 0x55E9A305 (Windows.UI.Xaml.dll) in appname.exe: 0xC000027B: an internal exception occurred for the application (parameters: 0x127DC468, 0x00000005). ''

A crash occurs when a user tries to display a second image. All decompressions are complete, and all bitmaps were created by this time.

I took advantage of the Build settings and narrowed down the difference to the option “Compile with .NET Native Tool chain”. If this option is checked, the application crashes. If this option is not checked, the application works fine.

It is said that the application uses about 400 MB of heap, therefore, although not a little, it is not located near the capacity of the machine.

“So uncheck!” I hear you cry. Unchecking this will cause the certification to fail, as shown below:

FAILED Supported APIs • Error Found: The supported APIs test detected the following errors: -API OpenSemaphore in api-ms-win-core-synch-l1-1-0.dll is not supported for this application type. System.Threading.dll calls this API. -API CreateSemaphore in api-ms-win-core-kernel32-legacy-l1-1-0.dll is not supported for this application type. System.Threading.dll calls this API. -API ExecuteAssembly in uwphost.dll is not supported for this application type. StupidTest.exe calls this API. -API DllGetActivationFactory in uwphost.dll is not supported for this application type. StupidTest.exe has an export that forwards to this API. 

An empty project has the same failure if .Net Native tool chain compilation is not selected.

So my questions are:

Should generic applications use .Net Native tool chain compilation?

Is there any documentation about parameter values ​​in an internal exception, or somewhere else I can refer to troubleshooting?

In short, any tips for getting out of “This doesn't work if selected, but you have to choose it in order to get a certified” dilemma in which I find myself?

Answer 1

I struggled with this problem over the last few days, and I found the answer!

So, if you have not upgraded Visual Studio 2015 to version 1, do it. Since this error is an error in the compiler, and after the upgrade you can build the project using the Compile.Net Native tool chain option.

And yes, the four errors that the WACK tool uses are related to compiling your project without checking the .Net Native tool chain option in the Build menu in the Package.appxmanifest file.