Minecraft version: 1.19.2
Forge version: 43.2.11
Quark version: 3.4-398
Enabled mods: [Link]
Logs: [see end of post]
Using ATLauncher for a customized modpack

Currently experiencing the most bizarre issue I've ever seen: with Quark installed, Forge will hang during the loading process before the Mojang splash screen ever appears, and the Minecraft executable will display as "not responding" indefinitely (waiting doesn't fix it, I have to kill the process manually). Worst of all, there is no crash report of any kind when this issue occurs. The log simply stops reporting anything around the time I assume Forge starts to hang.

However, for some inconceivable reason, restarting my computer and attempting to run Minecraft within a short time after startup does allow the game to successfully load. Upon quitting and relaunching the game, or after waiting too long post-restart, the issue reappears and Minecraft will hang indefinitely.

I've tried reinstalling the current version of Forge; downgrading Forge to an earlier version; reinstalling the current version of Quark; using a different version of Quark; disabling various other mods that are reported to cause problems when installed alongside Quark; deleting Quark's config files and having them repopulate; redownloading the Java platform used by the game; and various other methods to fix the problem, but as of posting this, the only consistent solution I've found seems to be... restarting my computer from scratch, every single time I want to launch the game. Which is really annoying!

I have uploaded and saved three separate console logs to pastebin in order to illustrate the issue to the best of my ability:
The first log was captured during a successful launch of the game after restarting my computer, with Quark installed. [Successful launch with Quark]
The second log was captured during an unsuccessful launch of the game in which this issue occurred, performed immediately after the first with no changes of any kind. [Unsuccessful launch with Quark]
The third log was captured during a successful launch of the game, performed after disabling Quark (and two dependents, which I verified were irrelevant to the issue). [Successful launch without Quark]

i really hope i'm not just having the world's most protracted skill issue right now

Multithreaded mod loading was a mistake

While searching around for people who've had similar issues, I found a Github post reporting basically the same problem with another mod. Apparently this issue stems from an unintended race condition when the mod loads too quickly before a dependent, or something like that. I don't really understand it, but the post did at least inform me of the existence of the jps and jstack commands so I've got a log from that now. Hopefully it's helpful in some way.
[Stacktrace log for hanging Minecraft]

For anyone else experiencing the same issue, the post above describes a potential workaround that will allow Minecraft to launch successfully.

1. Open fml.toml in the config folder of your modpack or Minecraft instance.
2. Look for this option:

# max threads for parallel loading : -1 uses Runtime#availableProcessors
maxThreads = -1

3. Change the value of maxthreads to something other than -1. Results seem the most consistent with a value of 1, but slightly higher numbers might also work.

maxThreads = 1

4. Launch the game and wonder at modded Minecraft functioning properly again.

I tried this fix myself and Minecraft seems to consistently avoid the hangup now, so I'm confident in using it and recommending it to others until the root cause has been discovered.

Multithreaded mod loading was a mistake

Seems like this issue exists in the 1.18.2 version of quark as well. Could you hotpatch it potentially?