-
20 Oct 2008 12:35 PM #1
Application hangs at loading screen in FF3
Application hangs at loading screen in FF3
Has anyone else experienced this?
I realize my description that follows may be vague, but I'm hoping others have experienced this...
Upon loading my application, FF3 just hangs at the "Loading..." screen. I see that the entire GWT javascript gets loaded (using firebug I can verify this), but the loading panel doesn't go away and the app's main screen doesn't appear. The problem is, it's completely random. For the first half of the day, it will work fine. Then it starts to screw up.
Any suggestions?
-
20 Oct 2008 1:14 PM #2
I've seen this when an exception was thrown for some reason etc... I would guess that is what is happening here too.
GXT JavaDocs: http://extjs.com/deploy/gxtdocs/
GXT FAQ & Wiki: http://extjs.com/learn/Learn_About_the_Ext_GWT_Library
Buy the Book on GXT: http://www.apress.com/book/view/9781430219408
Follow me on Twitter: http://twitter.com/gslender
-
20 Oct 2008 1:20 PM #3
That's what I was thinking, but I did not see any exceptions bubbling up. I'll investigate a little further.
I am perplexed, though, that the error occurs in Mozilla but not IE... lol.. usually it's the other way around.
-
20 Oct 2008 2:03 PM #4
To be more specific, I've seen this when a Java Runtime exception is thrown, like a NullPointerException, ClassCastException, or IllegalArguementException. Javascript is unable to handle these specific exception types, so it stops execution completely. No information about a specific exception type being the problem will be available from the browser because it doesn't even understand that an exception was thrown in these cases. The way to fix this is to catch the generic Exception object.
-
20 Oct 2008 2:06 PM #5
I really do appreciate all your responses.
I am somewhat more at ease now, because you're probably both right.
I just found that we have a major database problem. That certainly would cause exceptions to be thrown lol.
-
20 Oct 2008 2:11 PM #6
when I added this to my app, I found a bunch of web-mode issues that were silently happening without browser errors.... worth adding
ErrorDialog just shows the error to the user... and I take it from there...Code:GWT.setUncaughtExceptionHandler(new UncaughtExceptionHandler() { public void onUncaughtException(Throwable caught) { ErrorDialog.handleError(caught); } });GXT JavaDocs: http://extjs.com/deploy/gxtdocs/
GXT FAQ & Wiki: http://extjs.com/learn/Learn_About_the_Ext_GWT_Library
Buy the Book on GXT: http://www.apress.com/book/view/9781430219408
Follow me on Twitter: http://twitter.com/gslender
-
20 Oct 2008 2:18 PM #7
Thanks man. I'll definitely add that.
Cheers


Reply With Quote