For some reason, when I read certain PDF files, when I scroll down, it will take it time to "catch up", and load the page.
I have a decent computer, and I don't see why it takes so long to render the pages?
Is there a way to make Adobe Reader completely load the PDF file into memory so it doesn't have to constantly catch up?
Here is an example of one that takes a while to load pages: http://life.iupui.edu/osi/student-orgs/_Assets/docs/Student%20Org%20Ma nual.pdf
Ok, maybe you need to provide some more information...
I have Adobe Reader 10.1.3 on Windows XP, using Firefox 14.0.1
When I click on the link you provided in your original post, I see the progress bar
for about 1 to 2 seconds, and then the entire document (33 pages) is completely downloaded on my computer. I can scroll up and down, jump to the last page and back - there is no delay whatsoever.
Maybe you have some limitations on your system that we don't know about?
No problem, but it's quite obvious from my post that I didn't mean "the time it takes to download the file to my computer."
Anyhow, what information would you like me to provide?
Here's my DirectX diagnostics report: http://pastebin.com/qrDJXPyD
The phenomenon doesn't occur on PDFs that are vector text only. It seems to only occur on documents where the pages were scanned directly and just thrown into a PDF as images, or that document I provided in my original post which contains some decorative background on every page.
Also note that I experiece this phenomenon on both Adobe Reader in the browser, Adobe Reader standalone, Adobe Acrobat, and even Foxit's PDF Reader.
axmann48 wrote:
For some reason, when I read certain PDF files, when I scroll down, it will take it time to "catch up", and load the page.
I have viewed your doc again, this time on a very similar system as yours, both in the browser, as well as in the standalone Reader.
The interesting thing is that I did, this time, observe a small time lag when paginating through the document; something like about 0.1 sec - is that what you are seeing?
I really don't know why this is happening on Windows 7 x64, but not on the much older XP system.
On the other hand, that 0.1 sec lag does not bother me enough to investigate it any further. If the lag was longer, then I would perhaps start watching the process with ProcMon or similar, to find out what activities are causing the delays.
North America
Europe, Middle East and Africa
Asia Pacific