[Background and problem description]
In Latex, various problems often arise;
Runaway argument?
{\contentsline {subsection}{\numberline {6.3}General comments o
! File ended while scanning use of \@writefile.
<inserted text>
\by
l.47 \begin{document}
This Runaway argument problem is often caused by incomplete Latex compilation, examples can refer to
https://tex.stackexchange.com/questions/66015/errors-in-tables-then-runaway-argument-at-begindocument
On offline Latex tools, an easy fix is to delete the .aux file and recompile. If the compilation is complete and the correct .aux file is generated, the problem will be solved. However, if the problem is not resolved and the recompilation is still incomplete, the Runaway argument will recur.
Online Latex tools such as overleaf often make these problems more difficult by adding some limitations.
For example, Overleaf has a compilation time limit, and when processing image files that take up a lot of space (for example, in order to solve the Type 3 problem, the eps image is curved to make the image larger), it is easy to time out.
=============================
[Problem Resolution and Explanation]
Here is a list of the methods we tried to succeed:
1. Re-create the Overleaf project
The Latex version of "Restart if something goes wrong". Although it works metaphysically, but we don't understand Overleaf's internal business logic, we guess the reasons are as follows:
For a newly opened project, there is no intermediate file before compilation, so it runs normally. And the old project:
1) A backup or log file is generated in Overleaf, which increases the compilation time
2) An intermediate file will be generated that will overwrite the previous one. During the process of continuous overwriting, other errors such as fragmentation may occur
--------------------------------
2. Extend the original Overleaf project
In order to maintain the original version control, here we choose to continue to adjust the original project.
Description of the problem: The Runaway argument is generated because of an aux error, and the aux error is due to incomplete compilation. In the online version, since our recompilation is still incomplete, aux and compile time exceed alternate.
Problem analysis: One of the reasons for incomplete compilation is that eps takes up too much space, and it takes too long to generate pdf online;
problem solved:
1) Under the premise of offline backup, delete online large-volume eps (for example, the name is abc.eps);
2) Use offline latex (including the epstopdf package, and there are also large-volume eps in the offline folder) to generate the pdf corresponding to the large-volume eps
3) Confirm the pdf name, for example, the name is abc.eps, and the pdf name should be abc-eps-converted-to.pdf
4) Upload pdf
Compile without error
Notice:
1) If you don't want to compile eps, even if pdf is uploaded, its eps should be deleted. Because once the system finds that eps and pdf do not match, it will recompile eps.
2) Naming of pdf
Benefit: mainly want to be compatible with the previous version (do not modify the code referenced in the picture in the original text). The principle is this, the system will first search for eps, and if it cannot be searched, the last successful version will be displayed (that is, for the file named abc.eps, the system will search for abc-eps-converted-to.pdf), so The name of the pdf needs to be the name after the convert. This allows reading of both eps and pdf files (but abc.eps).
Disadvantages: Since some of the eps mentioned in the text are missing, there will be a warning; if there is a corresponding eps image to be updated later, you need to generate a pdf and then upload it
=======================
Acknowledgments: Comrade Chen Qiong, Huazhong University of Science and Technology