AJAX response sometimes skip some bytes

RESOLVED WORKSFORME

Status

()

--
major
RESOLVED WORKSFORME
10 years ago
6 years ago

People

(Reporter: kurt, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.1) Gecko/2008071615 Fedora/3.0.1-1.fc9 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.1) Gecko/2008071615 Fedora/3.0.1-1.fc9 Firefox/3.0.1

Some AJAX responses result in some leaked bytes (80 or 90 bytes lost aprox).

In some point of AJAX response, this broken line can be observed:

<td><img src="cby_orders_files/tdtda%2520href.html" cby_orderview?cor_id="1429&amp;tab=data&quot;">1429</td>

The right lines is (observed in any other browser except FF3):

<td><img src="cby_orders_files/ordertype2.gif"></td>
<td>---</td>
<td><a href="http://uzoo.zentense.com/uzoo3/webapp/cby_orderview?cor_id=1429&amp;tab=data">1429</a></td>

Can be seen that the bytes in the middle are lost in FF3.

The bug results in a wrong page rendering as some bytes are skipped in FF3. I've confirmed bug in all FF3 (even nightly build). The same page works nice in FF2, Konqueror or IE.

Reproducible: Always

Steps to Reproduce:
1. It can be reproduced every time. It only happens in determined requests, but when happens, repeating the same request reproduces exactly the same behaviour.

Unfortunately I only have observed this behaviour in an intranet, not opened to public.

Actual Results:  
Page rendered wrong as AJAX response is used to create a table dynamically and some bytes are not present in response. Wrong line (FF3):


<td><img src="cby_orders_files/tdtda%2520href.html" cby_orderview?cor_id="1429&amp;tab=data&quot;">1429</td>

Expected Results:  
Right line (as of FF2 or other browsers):

<td><img src="cby_orders_files/ordertype2.gif"></td>
<td>---</td>
<td><a href="http://uzoo.zentense.com/uzoo3/webapp/cby_orderview?cor_id=1429&amp;tab=data">1429</a></td>


Unfortunately I only have observed this behaviour in an intranet, not opened to public. If needed I can give access to somebody to check the bug and eventually debug it.
Component: General → DOM: Mozilla Extensions
Product: Firefox → Core
QA Contact: general → general

Comment 1

10 years ago
What do you mean with "AJAX response"?
XMLHttpRequest? iframe?
(Reporter)

Comment 2

10 years ago
I meant XMLHttpRequest. 

I've been gathering information, and there is a JavaScript problem, but definitively has nothing to do with XMLHttpRequest. XML response was just right.

In the case I presented here, XML is processed by an script to generate an HTML table, but in FF3 and only in FF3 does not work and some bytes are skipped (maybe in document.writeln?). 

So, I am going to close this bug and I will investigate further to localize the problem with more precission and report it as a bug if needed.
(Reporter)

Comment 3

10 years ago
I meant XMLHttpRequest. 

I've been gathering information, and there is a JavaScript problem, but definitively has nothing to do with XMLHttpRequest. XML response was just right.

In the case I presented here, XML is processed by an script to generate an HTML table, but in FF3 and only in FF3 does not work and some bytes are skipped (maybe in document.writeln?). 

So, I am going to close this bug and I will investigate further to localize the problem with more precission and report it as a bug if needed.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
(Reporter)

Comment 4

10 years ago
I am sorry. This bug is really hard to catch. I only can reproduce it on production server. I am trying to create the same conditions on development server but it works there flawlessly.

Where I said that "definitively has nothing to do with XMLHttpRequest", I just was wrong. If I request the troubled XML data directly through browser and it is received nice, but when getting it through XMLHttpRequest, some bytes on a XML node are lost. All the rest of scripts and elements on that page seem to work fine so, the only thing that can explain the behaviour I am observing is XMLHttpRequest returning incorrect results. But can be noted that I've not been able to confirm that point entirely. 

This can give some clue: when I copy the database on development server and I repeat the same AJAX interactions that failed on production, they work in development, as if connection lag could have something to do with it (the most noticeable difference between development and production environment). I've also observed that behaviour is non-deterministic, even in production server. I mean, sometimes the page behaves bad, but the next time doing the same, it works.

I suspect that has something to do with threading (AJAX interactions are run in parallel, right?) so the bug manifests only when several things happen in a given sequence (what things? what sequence?), and if timing changes, behaviour changes. I suspect the bug may also depend on processor speed or number of cores, but just speculating.

I am sorry not being able to give better information, but this is the best I can do with a so hard bug. The only thing that I am sure of, is that it is a bug introduced on FF3, as never seen this behaviour in other browsers (this code has been working for years on all kind of platforms). The bug has been observed in Linux and Windows platforms, and is quite annoying.

I've also observed in web applications we develop, not in third party applications that may use tons of AJAX, so there will be something we are doing that triggers the bug. Unfortunately, as I only can observe the problem in production environment, I cannot debug aggressively, but I will try to gather more information. It will be time consuming.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
(Reporter)

Comment 5

10 years ago
It works nicely in Firefox 3.0.3 version
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago10 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
(Assignee)

Updated

6 years ago
Component: DOM: Mozilla Extensions → DOM
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.