[U8.1] Windows 8.1 Universal app的Windows项目在Debug中运行良好，在Release中启动时崩溃 [英] [U8.1]Windows 8.1 Universal app's Windows project works fine in Debug, crashes on launch in Release

问题描述

我有一个通用Windows 8.1应用程序（我的计算机运行的是Windows 10 Professional），我可以模拟Phone项目并将Phone项目部署到发布或调试模式的Windows Phone 8.1设备。没问题。

I've got a Universal Windows 8.1 app (my computer is running Windows 10 Professional), and I can emulate the Phone project and deploy the Phone project to a Windows Phone 8.1 device in Release or Debug mode. No problem there.

然而，当我尝试启动Windows项目时，应用程序在显示启动画面后崩溃，然后才显示我的应用程序的第一页。 

However, when I try to launch the Windows project, the app crashes after displaying the splash screen, before displaying the first Page of my app. 

我的电脑处于开发者模式（当我转到Project - > Store - >获取开发者许可证时，它说计算机需要处于开发者模式
和已经 开发者模式，并且不会要求我同意任何许可条款或类似内容。）

My computer is in Developer mode (when I go to Project -> Store -> Acquire Developer License, it says that the computer needs to be in Developer mode and that it's already in developer mode, and doesn't ask me to agree to any license terms or anything like that).

因为应用程序（尝试）在发布模式下运行，所以从调试模式启用的正常堆栈跟踪启用崩溃行为不会发生，但VS确实问我是否要打开
另一个 VS实例来调试它。 如果我说是，第二个VS实例说已经附加了一个调试器，虽然其他调试器是什么以及我如何找到它来获取信息，我不知道。 长和短，
第二个VS实例没用，并且没有给我任何信息。

Because the app is (trying to) running in Release mode, the normal stacktrace-enabled crash behavior from debug mode doesn't happen, but VS does ask me if I want to open up another VS instance to debug it.  If I say yes, the second VS instance says that there's already a debugger attached, though what that other debugger is and how I can find it to get information out of it, I have no idea.  Long and short, the second VS instance is useless, and gives me no information.

事件查看器告诉我："激活app [MyAppName]！应用程序失败了错误：远程过程调用失败。有关其他信息，请参阅Microsoft-Windows-TWinUI / Operational日志。"

The Event Viewer tells me: "Activation of app [MyAppName]!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information."

Microsoft-Windows-TWinUI / Operational日志告诉我："应用程序[MyAppName]的ActivateApplicationForContractByAppIdAsUserWithHost！App对于Windows.Launch合同失败，远程过程调用失败.."

The Microsoft-Windows-TWinUI/Operational log tells me: "ActivateApplicationForContractByAppIdAsUserWithHost of the app [MyAppName]!App for the Windows.Launch contract failed with The remote procedure call failed.."

网络搜索这些字符串没有任何用处，因此我转向此论坛寻求帮助。

Web searching for these strings has yielded nothing useful, thus I turn to this forum for help.

有一点需要注意：我的开发是在公司许可下完成的，该许可与我登录Win10机器的个人Microsoft帐户不同。 我将Visual Studio切换到公司帐户，以确保我能够在发布模式下实际运行它以便在Beta之前进行一些最终测试时，能够在该公司帐户下部署
应该是今天开始的。）

One thing to note: my development is done under a company license that's different than my personal Microsoft account with which I log onto my Win10 machine.  I switch Visual Studio over to the company account to make sure that I'll be able to deploy it under that company account when I get done being able to actually run it in Release mode for some final testing before Beta (which was supposed to have started today).

有人可以帮我一把吗？

谢谢，

Kyle Humfeld

Kyle Humfeld

在一天的发展中

推荐答案

Hello Kyle Humfeld，

Hello Kyle Humfeld，

据我所知，应用程序有很多原因可能会在发布模式下崩溃但不会在调试模式下崩溃例如，它可能与编译器优化或内存布局或初始化的差异有关，或者应用程序无法处理暂停
并正确恢复。因此，我建议您尝试使用以下内容分析崩溃转储。来自
的Windows调试器（WinDbg）
这里。

As far as I known there are many reasons that an app might crash in release mode but not in debug mode. For example it may be related with the compiler optimizations or differences in memory layout or initialization or the app doesn't handle suspend and resume correctly. So I will recommend you try to analyze the crash dump using the Windows debuggers (WinDbg) from here.

此外，您使用的某些API在这里也很有用。或者你有可能为我们分享一个repro简单的样品吗？

Besides, some API you used will be also useful here. Or is it possible for you to share a repro simple sample for us?

祝你好运，

Barry

这篇关于[U8.1] Windows 8.1 Universal app的Windows项目在Debug中运行良好，在Release中启动时崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！