＆QUOT;没有＆QUOT的白色屏幕; ＆QUOT; Internet Explorer无法显示该网页＆QUOT; [英] "White Screen of Nothing" "Internet Explorer cannot display the webpage"

问题描述

我们有一个ASP.NET网站，有时得到的页面锁定，没有内容，全白画面，最终在IE超时返回一个错误的IE页面标题Internet Explorer无法显示该网页。注意拼写。我们将此称为没有白屏幕。

We have a ASP.NET website that some times gets pages to lock up, with no content, all white screen, that eventually time out in IE to return an IE error page title "Internet Explorer cannot display the webpage". Note the spelling. We refer to this as the "White Screen of Nothing".

从IIS日志，显示没有错误（不超过400个状态codeS），而事实上，显示IE浏览器在进入了没有白屏幕，作为状态code 200页IIS日志。此外，内部服务器端的ASP.NET跟踪，显示所有code正在按预期运行。

Logs from IIS, show no errors (no 400+ status codes), and in fact, show the page that IE goes into the "White Screen of Nothing" for, as status code 200 in the IIS logs. Also, internal server-side ASP.NET tracing, show all code running as expected.

试图重现此错误是困难的。它不会出现一致。在最好的，如果我们打开网页，关闭它们，并以最快的速度，我们可以重复这一点，它最终将发生在试图打开一个页面和/或帧的refesh。它并不总是在同一页的两倍。

Trying to reproduce this error is difficult. It does not occur consistently. At best, if we open pages, close them, and repeat this as fast as we can, it will eventually happen on attempt to open a page and/or the refesh of a frame. It is not always the same page twice.

有些使用AJAX控件。大多数使用GridView的。一些用Responce.Redirect。没有一致的。

Some pages use AJAX controls. Most use GridViews. A few use Responce.Redirect. Nothing consistant.

搜索了没有白屏幕或Internet Explorer无法显示该网页是所有的地方，也似乎没有关系。

Searches for causes of the "White Screen of Nothing" or the "Internet Explorer cannot display the webpage" are all over the place, and do not seem to be related.

我们已成功地将无白色屏幕的陷阱一个实例，而在Visual Studio 2008中调试会话，其中一个奇怪的，未知的线程被锁与下面的调用堆栈。请注意，我不知道是肯定的，如果这个调用堆栈相关的或即使是真正锁上。

We have managed to trap one instance of the "White Screen of Nothing" while in a Visual Studio 2008 debug session, where a weird, unknown thread was locked with the call stack below. Note, I do not know for sure, if this call stack is related or even if it was truly locked.

[托管到本机过渡]

[Managed to Native Transition]

System.dll中！System.Net.SafeCloseSocket.InnerSafeCloseSocket.Accept（System.Net.SafeCloseSocket socketHandle，字节[]的SocketAddress，楼盘INT socketAddressSize）+ 0x13字节
    System.dll中！System.Net.Sockets.Socket.Accept（）+ 0x73字节
    WebDev.WebHost.dll！Microsoft.VisualStudio.WebHost.Server.OnStart（未使用的对象）+ 0x35字节
    mscorlib.dll中！System.Threading._ThreadPoolWaitCallback.WaitCallback_Context（对象状态）+值为0x2F字节
    mscorlib.dll中！System.Threading.ExecutionContext.Run（System.Threading.ExecutionContext的ExecutionContext，System.Threading.ContextCallback回调，对象的状态）+ 0x6f字节
    mscorlib.dll!System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(System.Threading._ThreadPoolWaitCallback tpWaitCallBack）+ 0x53字节
    mscorlib.dll中！System.Threading._ThreadPoolWaitCallback.PerformWaitCallback（对象状态）+ 0x59字节

System.dll!System.Net.SafeCloseSocket.InnerSafeCloseSocket.Accept(System.Net.SafeCloseSocket socketHandle, byte[] socketAddress, ref int socketAddressSize) + 0x13 bytes System.dll!System.Net.Sockets.Socket.Accept() + 0x73 bytes WebDev.WebHost.dll!Microsoft.VisualStudio.WebHost.Server.OnStart(object unused) + 0x35 bytes mscorlib.dll!System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(object state) + 0x2f bytes mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x6f bytes mscorlib.dll!System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(System.Threading._ThreadPoolWaitCallback tpWaitCallBack) + 0x53 bytes mscorlib.dll!System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(object state) + 0x59 bytes

在该堆栈的所有功能都涉及到code，我们写了。我们做了Internet Explorer无法显示该网页，并呼吁在跟踪功能的各个方面，并没有在搜索似乎是相关的。

None of the functions in that stack are related to code we wrote. We did searches on "Internet Explorer cannot display the webpage" and various aspects of the function called in that trace, and nothing seems to be related.

任何想法？

推荐答案

我最后一次处理这样的问题，这个问题是时间太长的响应，和/或IIS回收工作进程。由于这就像一个资源问题（试图做一些事情，需要太多的时间，CPU或内存），修复的细节会有所不同。

Last time I dealt with an issue like this, the problem was a Response that was taking too long, and/or IIS recycled the worker processes. Since this is like a resource issue (attempting to do something that requires too much time, CPU, or memory), the specifics of the fix will vary.

PerformWaitCallback，仅仅是一个非同步应用打住，如果它是在东西是非常缓慢的等待可能的地方。

PerformWaitCallback, is just a likely place for an asynch app to come to a halt if it is waiting on something that is very slow.

这篇关于＆QUOT;没有＆QUOT的白色屏幕; ＆QUOT; Internet Explorer无法显示该网页＆QUOT;的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！