Memory Leak ?

[drbsoftware]

When looking at successive uses of PDF Viewer in Chrome, it appears that the WorkerTransport destroy is never called when the viewer is destroyed.

This means that the pageCache and other storage remain in memory.

I don't know if this is properly a PDF Viewer problem or a PDFJS problem, but it means that Sencha apps making extensive use of PDF Viewer may run themselves out of memory.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[drbsoftware]

I think PDF.js destroy needs something like:

        if (me.pdfDoc) {
            me.pdfDoc.destroy();
            delete me.pdfDoc;
        }

[SunboX]

yep, you are right. I will implement it.

Thanks for the hint! :)