This is a very general question, but it is based on a specific problem. I created a PDF reader for iPad and it works great, except for some PDF pages that always cause the application to crash. Now we find out that the same pages crash Safari, as I began to suspect that the problem is somewhere in the Apple pdf rendering code.
From what I could see, the crash pages cause the rendering libraries to start distributing memory as a mind until the application is killed. I have nothing else to help me determine what causes this process.
This does not necessarily happen with the largest documents, or with the largest forms. In fact, we did not find a single parameter that will help us predict which pages will break and which will not.
Now we just discovered that launching pages through a consumer program that allows you to combine documents is getting rid of the problem, but I could not determine which attribute or element it is key. Manually changing documents is also not an option for us in the long run. We need to start the automatic process on our server.
I hope someone with a deeper knowledge of the pdf file format can point me in a reasonable direction to look for document functions that can cause this behavior. All I have found so far is something about JBIG2 images, and I don’t think we have such.
safari objective-c iphone pdf ipad
Felixyz
source share