Alex Rivera | Logout

App crash - "DiskImageCache: Could not resolve the absolute path of the old directory."

Asked 2012-05-04T11:24:46.180
16

I am working on an app, where I display the data entered by user in a PDF file. PDF File is also created dynamically.

All this is fine.

I have implemented QuickLook framework to display the pdf file. When I call the QL framework, PDF file id displayed quite fine but when come back to the calling screen, my app crashes without any crash log or memory warnings.

I am calling QL with below code:

[[self navigationController] presentModalViewController:qlPreviewer animated:YES];

logs created are

DiskImageCache: Could not resolve the absolute path of the old directory.
[Switching to process 3070 thread 0x17603]
[Switching to process 3070 thread 0x15503]

This is quite interesting..... When I run the same program in Instruments to check for leaks and Memory Management, i can only find leaks when PDF document is scrolled and all the pages are viewed. However, interestingly there is no app crash that I can see. Also, I did try with ZombieEnabled = YES and without it but no app crash with Instruments.

I am quite clueless on how to interpret this and have been trying different things to solve this. Also, I have tried UIWebView but the result is the same.

I was again trying something to check out the issue and found something interesting. When i execute the code directly from X-Code - i get the crash in as explained above.

In other instance, if I execute the app by clicking on the app in the sim... no crash

I am yet to check this on device. Can someone confirm the crash on the device?

Also, Google does not have answer to this question.

Thanks in advance for your answers. Can anyone shed some light on this?

Edit
Report

1 Answer

1

@JimP, It isn't an iOS 5.1 bug. It has just started happening to my app as well, on iOS5.0. It seems to only affect pdfs of more than one page length, and seems to trigger most commonly on scrolling past the end of the document (although sometimes earlier also). It also seems to happen more often on a second load.

answered 2012-05-06T04:12:51.283

Your Answer