Closed Bug 343319 Opened 19 years ago Closed 11 years ago

Acrobat large PDF file says damaged but firefox 1.5.0.4 download ok

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Version:
3.6 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: w.langdon, Unassigned)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4 Firefox down loads large PDF (33MB, approx 1min). If file is explicitly saved to disk Acrobat 5.05 24/09/2001 can open it ok. Unix diff says file down loaded from URL is bitwise perfect. Indeed Firefox/Acrobat can read back file and display it ok if firefox File|Open file is used to read disk file. However if firefox is asked to display PDF it calls acroread 5.05 24/09/2001 which produces caution box saying 'The file is damaged and could not be repaired'. Reproducible: Always Steps to Reproduce: 1. point firefox to http://www.cs.ucl.ac.uk/staff/W.Langdon/ftp/papers/csrp-98-10.pdf 2. wait for download to finish (33MB) 3. acroread gives blank screen inside firefox window and acroread caution box pops up saying 'The file is damaged and could not be repaired'. I have tried this three times and the error occured each time. I do not think the file has been corrupted by crossing the network. One time firefox got stuck in a cpu hungry loop and I aborted it using the windowsNT task manager. Expected Results: Display first page of scanned document. The acroread caution box seems to be generic rather than specific to firefox but I have not found anything useful about why it gets triggered (other than s/w other than firefox also produces it). NB work around is to save PDF to disk and then read it back. Either using firefox or standalone acroread.
Can you try updating to a recent Acrobat Reader version like 7.0.8? 5.0.5 is _really_ old.
(In reply to comment #1) > Can you try updating to a recent Acrobat Reader version like 7.0.8? 5.0.5 is > _really_ old. The version of firefox is upto date. I have installed acrobat reader 7.0.8 16/05/2006 and the problem remains. Ie clicking on the csrp-98-10.pdf link causes firefox to download the PDF (80 secs) and then a caution box with the message "the file is damaged and could not be repaired". After dismissing it (by clicking "ok") the firefox status line has a message "An error has occurred while trying to use this document". This is with firefox version: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Summary: Acrobat 5.05 large PDF file is damaged but firefox 1.5.0.4 download looks ok → Acrobat large PDF file says damaged but firefox 1.5.0.4 download ok
Problem now occuring in Firefox 1.5.0.7 (updated today). -Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7 Running on Win2K - did not happen on previous version (1.5.0.6). Acrobat Reader 7.0.8 Example URL - http://euro.palm.com/europe/en/support/handbooks/LifeDrive_Handbook_en.pdf Acrobat plugin reports 'The file is damaged and could not be repaired' Works OK on IE!
Reporter, do you still see this problem with the latest Firefox 2 and the latest Adobe Acrobat? If not, can you please close this bug as WORKSFORME. Thanks!
Version: unspecified → 1.5.0.x Branch
Dear Steve, I am in Canada at present and so am _not_ using the orginal system which had the problem (windows based) but a Linux system with a totally different PDF viewer. Essentially the problem does not appear in the current system. Down load time is 20 minutes. The PDF viewer opens automatically on download completion and displays the first page. GNOME PDF Viewer 2.10.0 Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20070226 Firefox/2.0.0.2 Since the original fault was system dependent I am not sure this is a fair indication that it has been fixed. Bill W. B. Langdon, Computer Science Memorial University of Newfoundland St. John's, NL, Canada A1B 3X5 http://www.cs.mun.ca/~blangdon/
Dear Steve, Have just tried again from windowsXP and the problem is still here. Also I noted the blank screen does not refresh properly but I suspect this is unchanged from when the bug was reported. Firefox: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4 Acroread 7.0.8 <AdobeIP#0000126> WindowsXP professional 5.1 2600.xpsp_sp2_gdr (service pacek 2) 3GB W. B. Langdon, Mathematical Sciences, University of Essex Wivenhoe Park, Colchester CO4 3SQ, UK http://www.essex.ac.uk/maths/staff/langdon/
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
The problem is still here. I have just tried to load the PDF with SeaMonkey 1.1.18 Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20091022 SeaMonkey/1.1.18 The symptoms are much the same: SeaMonkey appears to load http://www.cs.ucl.ac.uk/staff/W.Langdon/ftp/papers/csrp-98-10.pdf and when it appears to have it, it displays an empty screen and the status line (rather than caution box) says "An error has occurred while trying to use this document". The cache size is 40 MB A pdf file 3247FAC7d01 is placed in .mozilla/default/Cache/ but removed again I hope this helps Bill
Seamonkey 1.1.18 is pretty old, can you update to seamonkey 2.0?
I have just tried serveral more times under microsoft windows. The bug is also there but the symptoms are slightly different. The first time I tried the cache was 10MB and the second I increased it to 40MB. This made no difference. In both cases SeaMonkey 1.1.9 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 appears to download the PDF file successfully. SeaMonkey updates the status message in its (still empty) window to "Done." It next starts Adobe Reader 8.1.2 which creates a blank grey window an immediately issues a digalogue box saying "The file is damaged and could not be repaired." When the dialogue box is dismissed by clicking on it, SeaMonkey updates the status line in its still empty window to say "An error has occurred while trying to use this document." Bill
I have just installed the latest version of SeaMonkey (2.0.4 identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 SeaMonkey/2.0.4) There is no difference from the behaviour I reported at 2010-04-19 01:21:24 PDT the cache remains at 40MB. Bill
I've also run into this problem and it is 100% a browser cache size issue. Test this as follows: 1) Set your cache size to be the size of the PDF to be downloaded. 2) try to download, observe the error 3) clear cache 4) Set your cache size to be the size of the PDF plus 5Meg 5) try d/l again, observed error again 6) repeat and increase cache in increments of 5M until suddenly it works Usually for me the cache size needs to be about 20% greater than the size of the PDF to be downloaded and it also needs to be cleared; if you have a cache with actual content in it then the required cache size is some variable amount greater than that.
Dear Joel, Thanks for this. To confirm if I set the cache to 73 MBytes (csrp-98-10.pdf is 33581655 bytes) clear the cache and then load the PDF all is well. Ie SeaMonkey 1.1.18 Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20091022 SeaMonkey/1.1.18 loads the file and starts acrobat which displays the PDF in the same window.
Bill, No problem. Hopefully the workaround of increasing cache size doesn't reduce the importance of this bug. I work for a e-publisher and this behavior, to users, is very confusing since there is no indication of what went wrong with the PDF download: no alert, no content, nothing. I do hope that this behavior can be fixed - or at the very least the user can receive an alert about needing to increase their cache size.
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.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Dear Tyler, appolgies for no reply, I have changed jobs three times since I reported this bug. (I am at KCL http://www.dcs.kcl.ac.uk/staff/W.Langdon/index.html#contact for a few more months. I have just loaded from http://www.mozilla.com/en-US/products/download.html?product=firefox-3.6.3&os=win&lang=en-US from scratch. Ie I clicked the do not import anything installation option. It says I have Firefox 3.6.3 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 The problem is essentially unchanged. Ie it says it has downloaded the PDF, it starts acrobat (8.1.2) and immediately produces an Adobe Reader caution box which says "The file is damaged and could not be repaired". The supplied profile says it is using upto 50MBytes for cache. No proxy. Bill
Resolution: INCOMPLETE → FIXED
Please install acrobat 9.3.2 or later. uninstall your current one, then download and install from fresh. Also, create a new firefox profile.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Version: 1.5.0.x Branch → 3.6 Branch
ps: If I increase the cache size in the new profile to 73MBbytes (the PDF is unchanged) then it works. Ie the PDF is downloaded and the 34 page document is opened inside the firefox tab. Ie Joel Stevenson's work around continues to work as before.
I've tracked down more details. It appears to only be a problem with the server hosting the file does not handle HTTP Range requests. If I download exactly the same file from the same server but in one case with the server set to accept range requests, it works regardless of the FF cache size. If I try with the server not soliciting range requests then it fails when the cache size is set too low.
Note that I uninstalled and reinstalled Acrobat Reader and used a new FF profile.
My comment #19 has is described backward, FF on Win makes the range request, the server doesn't solicit it, but the result is the same. FF on Windows sends a "Range" and "If-Range" header in the request and if the server supports range requests then FF and the server proceed through the byte ranges (which hands off to the Acrobat Reader plugin fine), otherwise the server returns the whole file in a single 200-status response (which results in an error with the plugin).
Windows XP SP2, running Mozilla/5.0 (Windows NT 5.1; rv:12.0a2) Gecko/20120307 Firefox/12.0a2, Adobe Reader 10, the browser was able to load the pdf file, i did not encountered any problems while reading or browsing thru the document.
Confirmed fixed on Firefox 23 on Windows 7 using PDF.js.
Confirmed fixed in FF24 on Win7. Changing flag to resolved fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago → 11 years ago
Resolution: --- → FIXED
Normal practice is to use WORKSFORME when a bug goes away without knowing what specifically fixed it :)
Resolution: FIXED → WORKSFORME
Thanks, I think I meant to use worksforme, but goofed. I'll double check in the future. I'm trying to help clear out old bugs
You need to log in before you can comment on or make changes to this bug.