Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post May 25, 2011 07:11 AM by GPankaj
May 25, 2011 04:19 AM|LINK
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".
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
Some pages use AJAX controls. Most use GridViews. A few use Responce.Redirect. Nothing consistant.
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.
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, 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
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.
May 25, 2011 05:21 AM|LINK
Check in your database if there are any locks appearing when you are opening and closing forms. I am suspecting some of your tables are getting locked and therefore other pages that are displaying data from locked tables may fail.
I am not sure this is the only cause. This is just another direction you can investigate.
May 25, 2011 07:11 AM|LINK
Check the event viewer if any error is reported. You must be having long running Stored Procedure and this might cause timeout which eventually must have displayed the error. Run the IE diagnoatic tool. Check the link below
You can open SQL profiler and see which objects are taking longer time to execute. Is there any memory leaks in your application. You can download the process explorer to further investigate the issue.
Hoper this helps