Closed oduros closed 3 weeks ago
Thanks for your report. Unfortunately the log messages show nothing suspicious. Generally, the extension will continuously output a lot of messages when heavily computing. In your case, all parsings are done at 22:49:41.180. After that, no parsing or computing are performed.
You may want to check the name of thread that is using CPU. In some cases, pdflatex will get stuck after compilation.
Another thing I can suggest is to exclude folder _pgfcache0
from being parsed. We have a config with term exclude
, you may search for that.
Thank you for your quick answer.
I do not know where exactly to look for the name of the thread using CPU. top
command will just mentions it is codium, and VSCodium process explorer gives all my processes at 0%, even if linux process managers says one core is 100%. The load does go back to normal usage when LaTeX workshop extension is restarted (without exiting VSCodium window it was ran).
About the exclude
config, you mean the one under "Latex-workshop › Latex › Search › Root Files: Exclude" ?
After some careful check, I think it might come from the default "Build" recipe I was using (latexmk). Maybe because this did not consider pgfcache
package needs to be run with option --shell-escape
(github/dionhaefner/pgfcache), but I am not sure this package is the actual issue. Anyway, the recipe I need (pdflatex -> bibtex -> pdflatex * 2), with correct option given to pdflatex tool, works and exits with normal CPU load, if that may help anyone else.
Pre-checks
Environment
The Issue
Reproduction Steps
Logs
LaTeX Workshop Output*
(sorry about the length)
Developer Tools Console
Anything Else?
LaTeX compiler outputs with 41 errors, that are mainly over/underfull boxes and bad referencing of some labels (because some things are still to do). The few other less common errors are:
I can provide privately my files if needed.
Thanks a lot for your work.
Probably related to : #2073