Something strange is happening with VerticalView of poppler-qml-plugin.
When destroying the page displaying the PDF, the VerticalView in QML
reports that it is being destroyed (I added Component.onDestruction:
print("destroying VerticalView"), but it is not yet being fully
destroyed, and in C++ when calling .isNull() on the VerticalView, it
appears to return false.In ucheader.cpp we detect a change in the header visibility (it is made invisible because it is also being destroyed) which triggers an update in the flickable margins. We always first check there that the flickable is still valide using m_flickable.isNull(), which reports that the flickable is still valid. However, when calling functions on m_flickable, we get a segfault. This is weird and requires further investigation. But I will attach a branch with a workaround for the document viewer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1577277 Title: Document Viewer app freezes/crashes on clicking back from pdf files Status in Canonical System Image: Confirmed Status in Ubuntu Document Viewer App: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Device: mako Channel: rc-proposed App freezes every time on clicking back arrow when trying to close pdf files and go back to the documents list. The only solution seems to be closing the app every time I want to open other pdf. On some occasions, the app will crash by itself when getting out of an pdf. [EDIT]: Former DocViewer contributor Stefano Verzegnassi took a look at this bug so I'll just paste his response here: I've found a few minutes for having a look at this issue, and I guess this has nothing to do with Document Viewer. The component which causes the issue hasn't received any update since an year. The issue in the DocViewer seems to be the same described in bug #1568016, which sounds to me as a regression in the UI Toolkit. During the last months a lot of regressions have been introduced with any UITK update, because critical changes are directly committed to a stable target. As long as core apps should always target the latest version of the toolkit, it should also be granted that a new toolkit update does not break any core app functionality. Anyway, since the UITK team is actually rewriting many components, I suspect the faulty component of the PDF viewer should be entirely rewritten too, since there's a small chance the issue gets fixed upstream (and that's what they did with the issue at the link below). I'm no more an active contributor of the Ubuntu Document Viewer, and whoever will join the team should also take care of fixing this. https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui- toolkit/+bug/1568016 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1577277/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
