Thrown NS_ERROR_NOT_INITIALIZED exception from com.google.gwt.xhr.client.XMLHttpRequest

I am developing an application using GWT in version 2.5.1.

A few days ago, we found in our magazines that there are a huge number of exceptions (a few per second !!!) that look like this:

Nov 5, 2014 6:00:45 PM com.google.gwt.logging.server.RemoteLoggingServiceUtil logOnServer SEVERE: (NS_ERROR_NOT_INITIALIZED) : com.google.gwt.core.client.impl.SerializableThrowable$ThrowableWithClassName: (NS_ERROR_NOT_INITIALIZED) : at Unknown.ZHe(StackTraceCreator.java:174) at Unknown.WFe(StackTraceCreator.java:508) at Unknown.IHf(Exceptions.java:29) at Unknown.pIb(XMLHttpRequest.java:164) at Unknown.OMe(RequestBuilder.java:411) at Unknown.anonymous(XMLHttpRequest.java:351) at Unknown.gHe(Impl.java:189) at Unknown.jHe(Impl.java:243) at Unknown.anonymous(Impl.java:70) 

In at least two cases, the problem occurred when the application was used in the Mozilla Firefox browser. To prevent this from happening, it was not enough to close the browser, as well as kill the process from the Task Manager. But I'm not sure that it cannot be started by another browser.

I also found this comment in the com.google.gwt.http.client.Request class, with the cancel () method:

 /* * There is a strange race condition that occurs on Mozilla when you cancel * a request while the response is coming in. It appears that in some cases * the onreadystatechange handler is still called after the handler function * has been deleted and during the call to XmlHttpRequest.abort(). So we * null the xmlHttpRequest here and that will prevent the * fireOnResponseReceived method from calling the callback function. * * Setting the onreadystatechange handler to null gives us the correct * behavior in Mozilla but crashes IE. That is why we have chosen to fixed * this in Java by nulling out our reference to the XmlHttpRequest object. */ 

I have no knowledge of how queries work, but I wonder if, in some cases, new versions of Mozilla Firefox will not cause this solution to be higher.

I would also like to add that the problem arises by chance, and I could not reproduce it on demand.

Do you have an idea what is the source of the problem, and could you give us any advice on how to solve this problem, or maybe a workaround, on how to deal with it?

Thank you in advance!

+7
firefox gwt
source share

All Articles