Memory leak? Definitely.

Crashing and artifacting stops after installing a second DIMM.

Upon loading or reloading a resource pack (F3+T and/or from the menu in-game or on the main menu) in 1.15, the game will artifact significantly (sometimes with a big of scattered lag) and proceed to crash between 5-30 seconds later. No crash report is generated (sometimes hs_pid logs appear), and other programs may be destabilized by this as well.

Minecraft is doing this independently of any software.

How to reproduce:

-Enter into a Minecraft world

-EITHER Switch between resource packs, reload resource packs (either using F3+T or menu) until something goes wrong. It takes me around 5-10 reloads. 128x128 is the size I'm using.

-OR Focus out of game using the Windows key until it refuses/doesn't 'hear' one time. The next time you attempt to reload packs, the game will crash possibly taking another program with it.

*This does not occur in 1.14.4

*RAM has been tested using MemTest. There are no issues there.

*Changing Java preference or modifying memory allocation does not change outcome

*Exiting and re-entering a world does not change outcome

*Crashes can be averted (regarding other programs) if you are fast enough to tab out at the sign of corruption (if there is one) and End Task, trigger a manual crash, or ALT-F4

*Seemingly, the larger the OS Page File, the longer it takes for Minecraft to destabilize everything. MC-167219 begins to come into play progressively.

========================

 CRASH REPORT: The crash report below was manually triggered after a failed reload (specifically, the artifact where all of the textures are white and tinted if biome-colored.

HS_PID.log / REPLAY_PID.log Crashes: No typical crash reports generate. Game may run into a couple of different issues after a pack reload (missing textures, extreme artifacting, loading bar on-screen will remain until crash while player can still look around, white screen). Crashes imminently and harms other programs upon this crash.

LAUNCHER_LOG.txt Crashes: This crash is occurs relative to Minecraft only (other programs are unaffected) and is immediate- however, despite the launcher giving me an option to see a crash report, none are generated. No hs_pid nor replay_pid logs for this one- a couple of launcher_logs had interesting bits:

(1: repeats an insane amount of times)

"[Info: 2019-12-14 04:50:27.6678835: GameCallbacks.cpp(142)] Game/cxg (Render thread) Info OpenGL debug message, id=0, source=API, type=ERROR, severity=HIGH, message=Unknown internal debug message. The NVIDIA OpenGL driver has encountered an out of memory error. This application might behave inconsistently and fail.
(pid=10984 javaw.exe 64bit)"

[Info: 2019-12-14 04:50:27.7448504: GameCallbacks.cpp(142)] Game/cxg (Render thread) Info OpenGL debug message, id=1281, source=API, type=ERROR, severity=HIGH, message=GL_INVALID_VALUE error generated. Invalid texture format.

(2: repeats for lots of textures, alternates between 'corrupt jpeg' and 'out of memory')

[Info: 2019-12-14 09:20:13.9488145: GameCallbacks.cpp(142)] Game/eaf (Server-Worker-17) Error Using missing texture, unable to load minecraft:textures/block/diorite.png
java.io.IOException: Could not load image: Corrupt JPEG

[Info: 2019-12-14 09:20:13.9472044: GameCallbacks.cpp(142)] Game/eaf (Server-Worker-16) Error Using missing texture, unable to load minecraft:textures/block/destroy_stage_7.png
java.io.IOException: Could not load image: Out of memory