TOPIC:

I'm creating a new PDFLayoutView, and a new Document, then doing Document.Open() and PDFLayoutView.PDFOpen().

Then when I want to view a second document, I'm doing PDFLayoutView.PDFClose() and Document.Close(), and creating a new Document (but reusing the PDFLayoutView).

I just noticed these warnings in my console:

"E/Bad Coding: Document object closed, but Page object not closed, will cause memory leaks."

Do I need to do something differently in my code? I see that the Page object has a Close() method, and I can get pages of the Document from the GetPage(n) method. But this seems like something that should be taken care of by the Document class.

to be sure: call PDFLayoutView.PDFClose() before Document.Close() invoked.
this log print when Page object finalized by GC, and Document object closed.

Yes, I'm calling PDFLayoutView.PDFClose(), then Document.Close().

I went back to test it some more, and now it's no longer happening. I don't remember which device I was using when I saw this yesterday. If I see it again, I'll post more info.