am i seeing wrong or is the game only using 3.6 GB ? which is normal ? what is wasting the other12 GB of memory?Originally Posted by Elizabeth.Grey Go to original post
Has nothing to do with the issue at hand.Originally Posted by Licher.Rus Go to original post
If your laptop has 16GB ram, it is not uncommon for the division 2 process to use about 4GB. Nothing out of the norm there.
But what we don't see in the screen capture, is what other processes are eating the rest of the 82% memory used. Based on the information we have, the issue lies somewhere else.
This is what's happening inside Task Manager sorted from highest to lowest, only The Division 2 is eating a chunk of memory.
The game is installed in SSD, and I don't think this is a memory leak on the hardware. The Division 2 is causing the memory leak issue.
Other games I played never reached at this level, and this is the only game I having issues ever since.
The one thing I observed is when you are playing The Division 2 for almost 2hrs.+ the memory usage keeps increasing.
And when it reached 85% that's where the lag and stuttering comes in.
MSI gaming laptop specs
![]()
It's definately a leak. 72% out of 16 GB - not normal.
Most of the time Division consumes less than 4 gigs. Plus additional memory is reserved for it, so it's 50% at worst scenario.
Move to perfomance tab, at the bottom there will be a resource monitor.
Open it and you will see memory usage per application directly (including reserved memory).
As a guy that has spent a lot of my adult life with computers, memory usage should not be the factor here. I mean, you can usually safely allow allocation of up to 99% of the available memory pool before memory is becoming the issue.
What I suspect is that you are most likely running the game off of a regular hard drive (HDD), not a solid-state drive (SSD). While a desktop hard drive can usually handle a game, a slower laptop hard drive will often struggle when loading game assets, thus causing stuttering and percieved "lag".
However, if your PC has an SSD, and only that, then there must be some kind of other issues.
The most common problems with laptops and performance are related to component cooling. If your components (CPU and graphics card in this case) runs too hot, they will reduce the clock-speed (called "thermal-throttling") to compensate for the heat output, thus lowering your framerate. I would suggest turning on the FPS counter in your Ubisoft overlay (Shift+F2 to open, and go to the settings - the cog-wheel icon, and tick the box for "Display FPS counter"). After that is done, play the game until you are noticing the lag, and then tell me the framerates you are experiencing when it happens.
Pretty sure thisOriginally Posted by THE_Crazy_Hyena Go to original post
Laptops has way worse cooling systems than desktops.
And even 'gaming' laptops are not made for many-hours game sessions
Difficult to figure out what the problem is with this limited info.
Confusing that in the 1st screenshot shows 3.6GB and the 2nd says 72% even though the overall memory usage is around the same level...
Crazy_Hyena might me right as well, the laptop getting too hot and triggering throttling could cause lag, especially after a few hours of gaming.
Try to use Process Explorer, it would give you more info on what's happening.
This is from Process Explorer and Resource Monitor. I don't think this is related to the GPU heating up, I can play Cold War Zombies, Ghost Recon Breakpoint, Microsoft Flight Simulator, Diablo 3, etc. non-stop all day without any lag at all.
The Division 2 is installed in SSD drive C:
I think I already figured out what's causing the sudden spike in memory usage, when I'm playing solo memory usage stays at 60% only. But when I joined a matchmake several times, that's when the memory usage spike to 85%.
And I think the memory allocated during matchmake is not properly dispose/release by the game.
Ghost Recon Breakpoint has better memory management compared to The Division 2. Whenever I matchmake several times memory usage is consistent, no memory spikes.
![]()