Auto-Refresh problem (with latex beamer)

Bug #1174697 reported by Benjamin Eltzner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qpdfview
Fix Released
High
Adam Reichold

Bug Description

I use the latest dailydeb on ubuntu 12.04

Steps to reproduce:
0. Let foobar.tex compile to foobar.pdf via PDFlatex.
1. Open foobar.pdf in qpdfview.
2. Activate auto-refresh.
3. Change foobar.tex such that references and page-links change (e.g. add a \pause in a latex beamer document).
4. Compile with PDFlatex, in 1/5 cases, qpdfview will go down.

Ubuntu provides a fancy errorbox with the option to restart the program, which does not work. But when I re-open foobar.pdf manually, I get an error box that says 'Could not open "/home/username/some/long/path/foobar.pdf".' while foobar.pdf is loaded without problem, so I guess this box comes from trying the ubuntu error box. Note that it literally says "username" not my actual username, so I guess if the problem is within qpdfview (which I find plausible, because I often used qpdfview while making presentations and today is the first time I repeatedly observe this behaviour), there might be some missing replacement somewhere.

Revision history for this message
Adam Reichold (adamreichold) wrote :

Hello,

This almost surely nothing do to with pdflatex or beamer, it is simply the problem of a incomplete PDF file sometime crashing Poppler. To prevent this, qpdfview tries to wait 500 ms if another change event for the is emitted until it tries to read the file, but if the processing within tex is complex, this might not be enough.

So to check this explanation, please try to increase the 500 on line 142 of file "documentview.cpp" to 750 or 1000 and check if the frequency of crashes is reduced.

Concerning the dialog boxes afterwards, I am not sure what happens there, because I am not familiar with Ubuntu's crash handler.

Best regards, Adam.

Changed in qpdfview:
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Benjamin Eltzner (b-eltzner) wrote :

I had quite favourable results with 750 and 1000 ms, so simply increasing the waiting time probably does the trick for most cases. (I only had a single crash with 750 ms and none with 1000 ms with about 15 tries at each setting.)

Revision history for this message
Adam Reichold (adamreichold) wrote :

Ok, since this seems to explain the problem, I am going to increase this to 750 ms by default and make it a "configuration-file only" setting (i.e. not expose it in the settings dialog). I'll mark this as fixed then.

Revision history for this message
Adam Reichold (adamreichold) wrote :

Ok, I feel the need to increase this even further than 750 ms you can use the setting "documentView/autoRefreshTimeout".

If you feel like it, you could mention "autoRefreshTimeout" and "prefetchTimeout" in the "documentView" section in the manual page?

Changed in qpdfview:
status: Incomplete → Fix Committed
assignee: nobody → Adam Reichold (adamreichold)
milestone: none → 0.4.3
Changed in qpdfview:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.