search

James-Yu / LaTeX-Workshop

Boost LaTeX typesetting efficiency with preview, compile, autocomplete, colorize, and more.
MIT License
10.47k stars 519 forks source link

Exceedingly slow compile times for large documents #4201

Closed HenryCarr98 closed 4 months ago

HenryCarr98 commented 4 months ago

Please fill the following fields with a star (*) and provide as much related information as possible.

Pre-checks*

Please change the following [ ] to [x] for confirmation.

  • [x] The issue has not been reported in this repository.
  • [x] The issue remains after disabling all other extensions and restarting Visual Studio Code.
  • [x] The FAQ cannot address the issue.
  • [x] The issue is not related to compiling a document, or the document can be successfully compiled in the OS terminal but not in Visual Studio Code with this extension.

Environment*

Please write exact version numbers instead of descriptors such as latest.

  • Operating System: [Mac OSX 14.1]
  • Visual Studio Code Version: [1.87.2]
  • LaTeX Workshop Version: [9.19.1]
  • TeX Distribution Version: [pdfTeX 3.141592653-2.6-1.40.25 (TeX Live 2023/Homebrew)]

Please list the environment and version number if you are using VSCodium, Snap or Flatpack versions of Visual Studio Code, and/or Visual Studio Code Remote Containers/SSH/WSL.

  • I am using XXX whose version is YY.ZZ

The Issue*

Please briefly describe the issue you come across.

  • Compiling thesis document and the extension loads, compiles fine for about an hour then the extension will either crash or become stuck in an infinite compilation loop. Rebooting VScode is the only valid fix and takes valuable time from my work.

Reproduction Steps

Please list out the steps to reproduce your bug. Include relevant environmental variables or any other configuration.

  1. N/A: simple large document compilation.

Expected Behavior

What were you expecting to see? Include any relevant examples or documentation links.

  • Document should compile

Logs

LaTeX Workshop Output*

Please paste the whole log messages below, not parts of ones. The log should start with New log placeholder %WS1% registered.

Here is how much of TeX's memory you used:
30128 strings out of 476025
577491 string characters out of 5779036
1885388 words of memory out of 5000000
48854 multiletter control sequences out of 15000+600000
587485 words of font info for 353 fonts, out of 8000000 for 9000
1141 hyphenation exceptions out of 8191
124i,21n,118p,2372b,1031s stack positions out of 10000i,1000n,20000p,200000b,200000s
</opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmbx10.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmex10.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi10.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi12.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi6.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi8.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmmib10.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmr6.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmr8.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy6.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy8.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/lm/lmss17.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/symbols/msam10.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/public/amsfonts/symbols/msbm10.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/urw/courier/ucrr8a.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/urw/times/utmb8a.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/urw/times/utmr8a.pfb></opt/homebrew/Cellar/texlive/20230313_2/share/texmf-dist/fonts/type1/urw/times/utmri8a.pfb>
Output written on main.pdf (182 pages, 10538349 bytes).
PDF statistics:
3248 PDF objects out of 3580 (max. 8388607)
2775 compressed objects within 28 object streams
699 named destinations out of 1000 (max. 500000)

Developer Tools Console

Please paste the whole log messages below, not parts of ones. This console logs can sometimes be very important in many cases. To access the log, click Help -> Toggle Developer Tools -> Console.

[Paste the log here. Do not remove the surrounding backquotes (`).]

Anything Else?

Add any other context about the problem below.

James-Yu commented 4 months ago

Not related to the extension. Try reducing system resource usage.

HenryCarr98 commented 4 months ago

Excuse me? How can you be so sure? Worked fine before the update

HenryCarr98 commented 4 months ago

@James-Yu this is plainly a problem with your extension. I've consulted with colleages who've all complained of similar issues with the extension. Today alone its crashed twice.

HenryCarr98 commented 4 months ago

@James-Yu A response would be appreciated.

James-Yu commented 4 months ago

This is not an extension problem. Additionally please kindly noted that the extension does not come with guarantee in any kind. Your provided information does not show anything wrong. I’m sorry but I cannot help resolve this issue.

jlelong commented 4 months ago

If you expect any kind of help, a clear description of this issue with the complete logs of the extension is required. You only posted the logs of the LaTeX compiler, which are pointless here. The Developer Tools Console may also show useful information.

HenryCarr98 commented 4 months ago

@jlelong @James-Yu How can I post logs when the very problem is it won't compile?

James-Yu commented 4 months ago

If that’s the problem, it is unrelated to the extension.

HenryCarr98 commented 4 months ago

It plainly is, my colleague can't compile on his machine. It's not an error, it simply stays compiling forever until I restart VScode then it works for about an hour

HenryCarr98 commented 4 months ago

@James-Yu Issue is persisting