GNOME Bugzilla – Bug 744986
Can't compile big document
Last modified: 2015-03-04 16:37:51 UTC
Hi, LaTeXila can not compile big document (typically 80/100 pages, part of thesis). The document can be compiled on the same computer with various LaTeX editors (gedit with the plugin, TeXmaker, Texstudio). When I start pdfLaTeX, the process run and then it is still alive but does not use the processor and LaTeXila stay waiting the end of the compilation. I don't know what can cause this bug, too big log file for LaTeXila or something else ?
In latexila, do you use the pdflatex command directly or do you use latexmk? It's maybe due to a parameter that is not present with other latex editors. With the all-output post-processor, does it work? Or no-output? If you know how to use the terminal, try to compile the document in the terminal, and run the same command in latexila. Can you also attach the output that you get when you run pdflatex in the terminal? Is the document private? If not, you can also send me a copy by mail so I can try to reproduce the problem so I can directly investigate the problem. Also, the bug is maybe fixed with the development version of latexila, since the build tools code has been rewritten and should now better support very long outputs.
Created attachment 297732 [details] output in the terminal at the first compilation this is the output of the first compilation. Just the bibliography has been compiled.
Created attachment 297733 [details] output in the terminal at the second compilation This the output of the second compilation. The size in less importante
I use pdflatex (latexmk has the same problem). I try with all-output : it does not work. I try with no-output : it works ! And if I use the classical command (pdflatex with latex output) after the no-output command, it works. I had the output of the terminal for two compilation. There are a big size difference (1.5 factor) between the first compilation(aftercleaning the aux file) and the second. It seems the bug depends of the size of the output file, isn't it ? I can provide the document if it is really necessary and helpfull, but this a lit bit sensitive. PS. modifying the post-processor of predefined command does not work, I had to create a new one, maybe this is a normal ?
Thanks for the provided information. So in latexila you use the available pdflatex command: > pdflatex -interaction=nonstopmode -synctex=1 $filename right? Did you use the exact same command to compile the document in the terminal? If you run latexila in a terminal and run the build tool, do you see some warning/critical messages in the terminal? The problem is maybe due to encoding conversion of the command output to UTF-8. The size is probably not important.
> PS. modifying the post-processor of predefined command does not work, I had > to create a new one, maybe this is a normal ? Yes it's normal, the default build tools are read-only. See bug #742542.
Yes I use this command in both cases. I see somes warning, but they are not critical (label, etc...), and there not error, a pdf is produced after compiled in the terminal. And you think the encoding change when the size of the latex document is important ? Ok for the read only command.
No, the encoding is not related to the size of the document or the output. But if it's an encoding issue you should see a warning message (from latexila) in the terminal. It's difficult to diagnose the problem just with what it's supposed to output. So if you don't see any message from latexila in the terminal, it'll be much simpler for me to diagnose the problem if I have the document. Also, with the document I would be able to see if the problem still occurs with the development version. Anyway, which Linux distribution do you use? With which version of TeXlive and pdflatex? The first line of 'pdflatex --version' returns for me (on Fedora 21): > pdfTeX 3.14159265-2.6-1.40.15 (TeX Live 2014)
(In reply to Sébastien Wilmet from comment #8) > But if it's an encoding issue you should see a warning message (from > latexila) in the terminal. Just to be a bit clearer, since I think you didn't understand well what I meant: 1. run latexila from the terminal: $ latexila 2. Be sure that the build files are cleaned (*.aux, *.toc, *.log, etc) 3. Then execute the pdflatex build tool from latexila. 4. See if there are some messages in the terminal.
I'm on Xubuntu 14.04, and the version of pdflatex is: pdfTeX 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian) yes I made that, but there is not error is the terminal. I can send you the file by mail if the help you (and if you keep it for you ;) !).
With the document that you sent me by mail, I can reproduce the bug with latexila 3.14. And I've tested with latexila 3.15 (the development version), and the pdflatex command runs fine \o/ I didn't investigate in details the problem, and since it'll be fixed for the next stable version (3.16), I think we can close this bug. Since there was a complete rewrite of the build tools system, it's difficult to know how to fix the problem in the previous versions (without backporting the whole new code).
Ok, that's a good news if the most recent version can compile the document ! I agree, further investigations are not really necessary. Does the version 3.16 will be in the ppa for (X)ubuntu 14.04 ?
(In reply to Kevin NADAUD from comment #12) > Does the version 3.16 will be in the ppa for (X)ubuntu 14.04 ? No, I don't think so. latexila 3.16 requires a more recent version of GtkSourceView, which requires a more recent version of GTK+/GLib, etc. If you have the time you can compile the sources with jhbuild, but it can easily take a half-day to setup correctly. Hopefully in the future there will be sandboxed/bundles applications, so it'll be much easier to install e.g. a recent version with all the dependencies: http://blogs.gnome.org/alexl/2015/02/17/first-fully-sandboxed-linux-desktop-app/