We have been chasing the same class from a different angle – not a crash inside it, but an unbounded leak. On iPadOS 26.6, every PDFDocument whose pages get rendered starts a VNRecognizeDocumentsRequest pipeline that is never released: roughly 2.7 OS threads and 20 MB per document, permanently. Our process reached 153 threads and 1.5 GB in under seven minutes of repeated document loads. It is not released by replacing PDFView.document, by deallocating the PDFView, or by time – with the app fully idle the thread count keeps rising. One thing that may save you time: usePageViewController(true, withViewOptions: nil) does not help with this. It reduces visiblePagesChanged: frequency, and in our measurements page changes on a stable document leak nothing at all – around 1000 of them left the footprint declining. The variable is newly rendered documents, not new pages. PDFView does carry -setDocumentAnalysisEnabled: / -isDocumentAnalysisEnabled, none of it public. With analysis off, our leak goes to exactly zero over 28 document loads. If you are facing the same issue, it would help if you also file feedback and suggest that these properties are made public. An analysis that never starts cannot crash – and in many cases the analysis is not relevant to the app.