Memory problem

I keep getting booted off due to a memory problem. The error code is in the spoiler below. Any help?

#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 1048576 bytes for AllocateHeap
# Possible reasons:
# The system is out of physical RAM or swap space
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# JVM is running with Zero Based Compressed Oops mode in which the Java heap is
# placed in the first 32GB address space. The Java Heap base address is the
# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
# This output file may be truncated or incomplete.
#
# Out of Memory Error (allocation.cpp:44), pid=42464, tid=39412
#
# JRE version: OpenJDK Runtime Environment Microsoft-32931 (17.0.3+7) (build 17.0.3+7-LTS)
# Java VM: OpenJDK 64-Bit Server VM Microsoft-32931 (17.0.3+7-LTS, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#

--------------- S U M M A R Y ------------

Command Line: -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Dos.name=Windows 10 -Dos.version=10.0 -Xss1M -Djava.library.path=C:\Users\astro\AppData\Roaming\.minecraft\bin\49e3a524a916ccfa727067d81932e2619930bbf8 -Dminecraft.launcher.brand=minecraft-launcher -Dminecraft.launcher.version=2.3.522 -DFabricMcEmu= net.minecraft.client.main.Main -Xmx8G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M -Dlog4j.configurationFile=C:\Users\astro\AppData\Roaming\.minecraft\assets\log_configs\client-1.12.xml net.fabricmc.loader.impl.launch.knot.KnotClient --username Astromath1959 --version fabric-loader-0.14.11-1.19.3 --gameDir C:\Users\astro\AppData\Roaming\.minecraft --assetsDir C:\Users\astro\AppData\Roaming\.minecraft\assets --assetIndex 2 --uuid 9240e783c15e4ebb97e5d2f7726ad057 -DEnHFeX1k --clientId NzMyNDdkODQtOGIyMS00OWNkLWE5ODctOTZjYmYyZmI2MWZm --xuid 2535434855099971 --userType msa --versionType release

Host: AMD Ryzen 7 5825U with Radeon Graphics , 16 cores, 15G, Windows 11 , 64 bit Build 22000 (10.0.22000.1219)
Time: Thu Dec 8 12:53:08 2022 Eastern Standard Time elapsed time: 90.242429 seconds (0d 0h 1m 30s)
.
[snip]
.
--------------- S Y S T E M ---------------

OS:
Windows 11 , 64 bit Build 22000 (10.0.22000.1219)
OS uptime: 15 days 13:55 hours
Hyper-V role detected

CPU: total 16 (initial active 16) (16 cores per cpu, 2 threads per core) family 25 model 80 stepping 0 microcode 0x0, cx8, cmov, fxsr, ht, mmx, 3dnowpref, sse, sse2, sse3, ssse3, sse4a, sse4.1, sse4.2, popcnt, lzcnt, tsc, tscinvbit, avx, avx2, aes, erms, clmul, bmi1, bmi2, adx, sha, fma, vzeroupper, clflush, clflushopt, hv

Memory: 4k page, system-wide physical 15722M (1602M free)
TotalPageFile size 40298M (AvailPageFile size 4M)
current process WorkingSet (physical memory assigned to process): 6380M, peak: 6414M
current process commit charge ("private bytes"): 17952M, peak: 17953M

vm_info: OpenJDK 64-Bit Server VM (17.0.3+7-LTS) for windows-amd64 JRE (17.0.3+7-LTS), built on Apr 20 2022 04:24:16 by "" with MS VC++ 16.10 / 16.11 (VS2019)

END.

Is your hard drive close to full?

Nope. My c: drive has 267 G free out of 476 G. My d: drive is completely free (931 G). And my external e: drive has 4.33 T free out of 4.54 T.

I have never figured out how to get java to access my d: drive. Actually, I have never figured out how to get any of my apps to access the d: drive.

p.s. The c: & d: drives are actually 2 partitions of one drive.

It is modded. However, not all the mods I used for 1.19.2 was updated for 1.19.3. So, I had to drop the un-updated mods.

EMC is still on 19.2, afaik, so using 19.3 is a likely suspect.

Ok. I was on when I was warned that the server was going to update to 1.19.3, so I assumed that it's now that version. Fortunately, I had renamed the mods folder before updating. I'll go back and see.

EDIT: I'm back on 1.19.2 and no more memory issues.

Now that we are officially on 1.19.3, I'm back to having memory problems. As soon as EMC starts, I get a memory out error.

You seem to be setting -Xmx8G in your client memory settings. Try reducing this number. Usually you only ever need at most 4G, the default is 2G.

Actually, I have it at 4.

Log says otherwise.

Yeah, that's the old one. However, I researched a solution. I had to add a variable to Advanced System Options. That seemed to do the trick.

Variable Name: _JAVA_OPTIONS
Value: -Xmx1024M

Drat. I'm still getting memory error, but it's no longer immediately kicking me off.

Where's the new log? It would be nice to confirm that that shows 1GB now.

Sorry about not showing the new log. I've managed to solve the problem myself. All I had to do was to double the size of my virtual memory. No more memory problem. Also, just to be on the save side, I added virtual memory to my D partition. Hopefully that will solve any future problems.

I didn't start having problems until 1.19.3. In fact, I'm still having problems, but they are fewer since I upped my virtual memory. I'll post a log next time it happens.