GNOME Bugzilla – Bug 745827
evince crashes with "ev_page_cache_get_annot_mapping: assertion 'page >= 0 && page < cache->n_pages'"
Last modified: 2015-10-16 16:47:41 UTC
Evince routinely crashes on me with: (evince:2867): EvinceView-CRITICAL **: ev_page_cache_get_annot_mapping: assertion 'page >= 0 && page < cache->n_pages' failed Steps to reproduce: 1) Make evince the default viewer for latexmk. Add the line "$pdf_previewer = 'start evince';" to your ~/.latexmkrc file. 2) Compile a reasonably large LaTeX file with "latexmk -pdf -pvc" 3) Open the file, add a LaTeX compile error somewhere in the middle and save it. 4) latexmk will automatically recompile the file and will fail on the compile error. 5) Fix the compile error, save the file again and type X into the latexmk prompt and hit Enter. 6) latexmk will compile the latex file again and this time, when evince tries to load it, it will crash. I've been hitting this bug constantly for a while now. It's gotten a little better in the last few weeks. It used to crash evince every time and now it only crashes it every other time or so.
Thanks for taking the time to report this. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!
Created attachment 298841 [details] Full Backgrace of the crash
I would have set it back to NEW but for whatever reason, bugzilla won't let me. In any case, a full backtrace is attached.
(gdb) bt full
+ Trace 234821
application = 0x7fe828d7b0e0 [EvApplication] context = <optimized out> error = 0x0 status = <optimized out> (gdb)
Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 735744 ***