If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Downloaded PDF is incomplete/corrupt with Camino

RESOLVED INCOMPLETE

Status

Camino Graveyard
Downloading
RESOLVED INCOMPLETE
10 years ago
10 years ago

People

(Reporter: George Slusher, Unassigned)

Tracking

Details

(Whiteboard: DUPEME [CLOSEME 5/22], URL)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

The PDF that is downloaded when clicking on "Download Instructions" is incomplete--only 144-172K of 2.5 MB, even though Camino's download window shows 2.6 MB downloaded.

Reproducible: Always

Steps to Reproduce:
1. Click on the "Download instructions" link
2. Wait a long time (10-20 seconds, at times) while the rainbow ball spins until the download starts.
3. When download finishes, wait longer while the ball spins again. 
4. Attempt to open the file.
Actual Results:  
The file is incomplete. It crashes Preview and Adobe Reader says that it is corrupt.

Expected Results:  
The file should be OK. I downloaded it with Firefox, Safari, and iCab with no problems.

Camino is really bad about downloading. It can spin and spin, while saying that it is waiting for the site. While this is going on, Camino will not do anything else. Eventually, it starts downloading. (It can take as much as 20 seconds to start downloading.) When the download is complete, there is often another period of spinning ball (3-8 seconds, sometimes longer), then the file is downloaded. This does NOT happen in Firefox, Safari (OS 10.3.9) or iCab. They all start downloading almost immediately. iCab downloaded that 2.5 MB file in less time than Camino took just to get started. It's almost enough to cause me to stop using Camino, which I've used since at least 0.8.

Comment 1

10 years ago
I have to run to work and don't have time at the moment, but I'm pretty sure the "Camino reports a file size that disagrees with reality" part of this is a dupe.

curl -I http://www.thinktankphoto.com/pdfs/ChangeUp_Instructions_Print.pdf
HTTP/1.1 200 OK
Date: Thu, 27 Mar 2008 11:14:43 GMT
Server: Apache/1.3.33 (Unix) PHP/4.3.10 FrontPage/5.0.2.2510
Last-Modified: Fri, 23 Mar 2007 23:01:43 GMT
ETag: "10fff-298c0e-46045c57"
Accept-Ranges: bytes
Content-Length: 2722830
Content-Type: application/pdf

so it's probably not a MIME type issue (which is the first thing I thought of when you said it works in Safari).

It downloaded fine for me, by the way. Does this happen on all PDFs for you, or just that particular one?
(Reporter)

Comment 2

10 years ago
Several on that site cause the same problem. Normally, I can download files OK, except for that annoying "wheel-spinning" that Camino tends to do at the beginning and end of downloads. iCab, Firefox and Safari are all faster in that respect. I have had a few corrupt files. 

I forgot to mention that I tried clearing the cache and turning off the popup and ad blocker, but that made no difference. Let me know if there is any more information you could use. 

Comment 3

10 years ago
Try using Troubleshoot Camino to test this with a fresh profile. This might be bad cache preferences.

http://pimpmycamino.com/parts/troubleshoot-camino
George, what page are you on when you click that link?  It may not be relevant, but it would be useful to know.

Also, you're just normal-clicking the link to download (i.e., you don't have the PDF Browser Plugin installed)?

Comment 5

10 years ago
George, can you please try comment 3 and answer comment 4?
Whiteboard: DUPEME → DUPEME [CLOSEME 5/22]
Closing INCO due to lack of updates.  If you can supply the requested additional information and the problem persists in Camino 1.6.1 or a recent trunk nightly, you may reopen this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.