为什么 Silverlight 在发布模式下会崩溃,但在调试模式下不会崩溃?

发布于 2024-09-05 09:51:34 字数 925 浏览 5 评论 0原文

我有一个 Silverlight 应用程序,它在调试发布模式下运行良好数周。

它在调试模式下仍然运行良好。

但是,现在当我在发布模式下运行它时,它会启动,向我显示屏幕,加载数据,然后挂起,并且浏览器(Firefox)关闭自动。我尝试过其他浏览器,但每个浏览器都会崩溃,例如 Chrome 会显示“Silverlight 插件已崩溃”。

以下是我得到的输出的最后几行:

'firefox.exe' (Silverlight): Loaded 'System.Windows.Controls'
'firefox.exe' (Silverlight): Loaded 'System.Windows.Controls.Toolkit'
'firefox.exe' (Silverlight): Loaded 'C:\Program Files\Microsoft Silverlight\4.0.50524.0\en-US\mscorlib.debug.resources.dll'
'firefox.exe' (Silverlight): Loaded 'C:\Program Files\Microsoft Silverlight\4.0.50524.0\en-US\System.Windows.debug.resources.dll'
The program '[1120] firefox.exe: Silverlight' has exited with code -2147023895 (0x800703e9).

如何获得有关在发布模式下崩溃时发生的、在调试模式下未发生的情况的更多信息? >

I have a Silverlight App that has worked well in Debug and Release modes for weeks.

It still works well in Debug mode.

However, now when I run it in Release mode, it starts, shows me the screen, loads the data, then hangs, and the browser (Firefox) closes automatically. I've tried other browsers and each of them crashes, Chrome says "The Silverlight Plug-In has crashed" for instance.

Here are the last lines of Output that I get:

'firefox.exe' (Silverlight): Loaded 'System.Windows.Controls'
'firefox.exe' (Silverlight): Loaded 'System.Windows.Controls.Toolkit'
'firefox.exe' (Silverlight): Loaded 'C:\Program Files\Microsoft Silverlight\4.0.50524.0\en-US\mscorlib.debug.resources.dll'
'firefox.exe' (Silverlight): Loaded 'C:\Program Files\Microsoft Silverlight\4.0.50524.0\en-US\System.Windows.debug.resources.dll'
The program '[1120] firefox.exe: Silverlight' has exited with code -2147023895 (0x800703e9).

How can I get more information about what is happening at the point of crash in Release mode that is not happening in Debug mode?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

萌逼全场 2024-09-12 09:51:34

似乎与您的问题相关。从底部的更新来看,似乎

用于的显示字符串
调试器触发程序路径
否则不会执行,并且
它进入了无限循环

This seems relevant to your issue. From the update at the bottom, it seems that

the display string used for the
debugger triggered a program path
which was not executed otherwise, and
there it entered in an endless loop

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文