442578 - XMLHttpRequest response is now limited in size.

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Jonathan]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14

With Firefox 1.5, and 2.0, I can request 10 pages of complex data from the server and display it in the browser using AJAX.

Using the exact same URL and code with Firefox 3.0, the data is truncated around 125,000 characters (UTF-8). With prior versions, I could return 320,000+ characters.

When I reduce the code's "pagebuffer" from 10 down to 4, the problem mostly disappears except when a page of UTF-8 data contains very long lines that push the response over 125K+ UTF8 characters.

The "pagebuffer" in my code is set at 10.  Using the URL provided, load the web app.  Then, in the webapp's top bar, click on "Hebrew".  Using the scrollbar, scroll down to close to 6177 of 23145.  As the XHR is processed, the response will be truncated midstream.  Firebug shows the truncated data.  This does not occur in FF2 or in some of the earlier versions of FF3.

The webapp is built on a javascript/php application framework explicitly for Firefox (4 years of development). The webapp itself is "PlowShare", an advanced interlinear Bible program that is possible only because of Firefox/Gecko.


Reproducible: Always

Steps to Reproduce:
1. Use the URL provide to load the javascript web app.  
2. In the webapp's top bar, click on "Hebrew".
3. Using the scrollbar on the Hebrew window, scroll down to close to 6177 of 23145.
4. An alert will be displayed and the entry will be logged in the "Log" window.
Actual Results:  
As the XHR is processed, the response will be truncated midstream.  Firebug shows the truncated data.  This does not occur in FF2 or in some of the earlier versions of FF3.  

An alert is displayed stating "COMMUNICATIONS RESPONSE FROM SERVER IS INCOMPLETE" and the entry will be logged in the "Log" window.

Expected Results:  
As the XHR is processed, the response will NOT be truncated midstream, but fully received into the XHR response variable.  This "paged" data will display in the window properly.

Comment 1

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 2

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.