Slow/Buggy Compilation with \input

Question

I've been noticing that some of my files take a really long time to compile. It'll often be sluggish to compile and then produce an "invalid or corrupted file" error for a long time before resetting and updating - sending me back to the top of the document. It's rather irritating and hard for me to typeset when the pdf resets its position back to page 1 and takes forever to compile even for a small change.

One of my guesses as to why this was happening was maybe the file size/inefficiency with compilation, so I made the following changes:

• Made a more minimal .sty file and removed some .tex shortcut configurations which could be buggy
• Made the file as minimal as possible by keeping the current inputs to a minimum on a document that has a master .tex file and multiple \inputs.
• Removing unnecessary formatting changes, e.g. fancy page headers/footers This all made the document much more simple and theoretically have less instructions to compile, but still it is taking forever to compile.

Then I thought it could be up to the fact that I used \inputs as I was testing my .sty file in another folder with a minimal test file - which seems to compile just fine. However, I went and removed a small section of that file to another test file and readded it as input, and it also became unbelievably slow.

Right now, I use \input as a way to take small notes and compile them into a larger document, but it seems like it is the reason that compilation is being so troublesome. Has anyone else had a similar issue, and is there any way to fix it (besides just compiling all notes on a large TeX file)?

Run Example: I used the following files:

\documentclass{article}
\usepackage[lecture]{random}
\begin{document}
\title{Notes}
\author{Revise}
\date{Fall 2021}
\maketitle
% toc
\tableofcontents
\input{15_tail_calls.tex}
\end{document}

%% Tail Calls
\section{Tail Calls}
\begin{tcbexample}[name = Lexical/Dynamic Scope, minted language = scheme]{
Lexical Scope: Standard way how names are looked up in Python/Scheme - parent of a frame is the frame in which a procedure is defined.

Dynamic Scope: Alternate approach to scoping, parent of the frame is the frame in which a procedure is called. Known as \lstinline{mu} special form in Scheme.
}
(define f (lambda (x) (+ x y))) ; P: global
(define g (lambda (x y) (f (+ x x)))) ; G - P: global, F - P: F1 (when using dynamic scope)
(g 3 7)
\end{tcbexample}

Here is the link to random.sty, the preamble package I am using.

This is the resulting .log output.

Latexmk: fls file doesn't appear to have been made.
Latexmk: Examining 'master.log'
=== TeX engine is 'pdfTeX'
Latexmk: Errors, so I did not complete making targets
Collected error summary (may duplicate other messages):
  pdflatex: Command for 'pdflatex' gave return code 1
      Refer to 'master.log' for details
Latexmk: Use the -f option to force complete processing,
 unless error was exceeding maximum runs, or warnings treated as errors.

Background: I use pdflatex as the compiler and latexmk on the side to help with compilation on VSCode.