I also use okular v1.3.3 all the time without the described issue.
It *might* have something to do with the _particular_ PDF you are
trying to open. I would suggest that, if possible, you attach the
failing PDF to this bug report.
Also, it's unclear (to me) from your description if the PDF which
is now failing used to work? *If* it did, *and* you still have a
working copy, *and* it is possible to attach it, then I would also
suggest attaching the (previously-)working PDF to this bug report.
Please ensure it is clear which (attached) PDF is failing, and also
which one is working.
Finally, any idea if there is, e.g., "excessive" memory consumption
or I/O?
I also use okular v1.3.3 all the time without the described issue.
It *might* have something to do with the _particular_ PDF you are
trying to open. I would suggest that, if possible, you attach the
failing PDF to this bug report.
Also, it's unclear (to me) from your description if the PDF which )working PDF to this bug report.
is now failing used to work? *If* it did, *and* you still have a
working copy, *and* it is possible to attach it, then I would also
suggest attaching the (previously-
Please ensure it is clear which (attached) PDF is failing, and also
which one is working.
Finally, any idea if there is, e.g., "excessive" memory consumption
or I/O?