It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
dikembe5: I have the exact same issue described by others in this thread. My card is RX 6750XT, up-to-date drivers, and the game fills up all 12gbs of VRAM after fast travelling, but I can recreate this by just entering and exiting Whiterun a handful of times. After that what happens in the first post happens to me as well, same RAM specs, and eventually it gets choppy and I get an unending loading screen, forcing me to kill the Skyrim process (using all of my RAM) in task manager.

Can anyone else confirm if the Vulkan solution mentioned above addresses this entirely?
It works very well for me. VRAM on my GTX 1080 stays around 4GB constantly. I mean, it fluctuates but the memory leak definitely isn't present. At least it doesn't seem to be. If you install DXVK, you may get some stuttering at first because it is creating its own cache file but it'll clear up. Performance seems to be the same, too. I've used DXVK for other games, it's a great mod but requires trial and error as it won't work for everything.
Has anyone contacted GOG about this? it's obviously a problem with their build :/
avatar
baronofdoom.547: It works very well for me. VRAM on my GTX 1080 stays around 4GB constantly. I mean, it fluctuates but the memory leak definitely isn't present. At least it doesn't seem to be. If you install DXVK, you may get some stuttering at first because it is creating its own cache file but it'll clear up. Performance seems to be the same, too. I've used DXVK for other games, it's a great mod but requires trial and error as it won't work for everything.
I've since tried it myself and can report DXVK works on my system as well. Everything is stable, VRAM and RAM issues all gone, performance is the same/as expected.
Post edited January 09, 2025 by dikembe5
avatar
dikembe5: I've since tried it myself and can report DXVK works on my system as well. Everything is stable, VRAM and RAM issues all gone, performance is the same/as expected.
Good to hear. DXVK is kind of an awesome mod, I used it on the original version of Outer Worlds and it completely cleared up the stuttering/hitching it was constantly doing.
The problem appears to be with the 1.6.1179.0.8 SkyrimSE executable file that is in the 0.1.3905696 GOG version - that is the only offline installer available - and is the latest of the two versions that is available through GOG Galaxy.

According to the UESP, the only change that was made for the 1.6.1179 version was to change the version number to differentiate the GOG version from the Steam one.

However, clearly something went wrong and introduced this memory leak.

Because, if you install GOG Galaxy and roll back to the only other available version (0.0.3895161), you will get an exe with the 1.6.1170.0.8 version number. And no memory leak. You can then take a copy of that SkyrimSE.exe file and copy it into an installation using the offline 0.1.3905696 installer, and you will also get the game with no memory leak.

The timestamps on the files that get changed by the update show a few additional changes - one of which is clearly shown by a change to the file size (HearthFires.esm from 3885KB to 3886KB). Since there is no changelog we cannot know what has changed - so we have the choice to use all of the older files that changed between 0.0.3895161 and 0.1.3905696, or just the exe.

The main point is that the exe is where the memory leak is, and replacing it with the older one will fix it.
avatar
LoRezJez: The main point is that the exe is where the memory leak is, and replacing it with the older one will fix it.
Thank you very much for this information LoRez. It didn't even occur to me the possibility of attempting to rollback!
That said, the major downside of this is that SKSE (script extender) does not support GOG's Skyrim 1.6.1170

So, right now we either opt to play "vanilla" (or non SKSE mods) while rolling back to a previous game version or use DXVK if desiring to install mods that require SKSE.
avatar
kehom: That said, the major downside of this is that SKSE (script extender) does not support GOG's Skyrim 1.6.1170
Does on my GOG 1.6.1170:)

dizet
Is there a memory leak in the regular version of Skyrim or just the Anniversary Edition/Content??
Galaxy or direct download or both? Might help to narrow down the list of potential causes, or to exclude certain potential causes. Just like it would be interesting to confirm if playing fullscreen or windowed or borderless (like one poster mentioned) really makes a difference.

When some users have a problem while others don't, then it's likely that the cause is somewhere on the side of the users having the problem. Which isn't saying that the users or their systems are the "culprits". Some software (or software settings) are simply incompatible with certain system configurations and / or components. But as long as the developers or maintainers don't know the details, they can't do anything about it.

In this context: Has anybody reported the problem officially to GOG, and does a problem ticket exist there? It may not help, but don't expect any action from them as long as nobody bothers to inform them officially. All they know from the forum posts is that a few players mention heavy RAM usage or RAM overflow - not much to work on.
Post edited March 08, 2025 by Greywolf1
I have the same issue. Thought it was a mod first, but no. The game keeps clogging up virtual memory until it eventually CTDs. Only got 8GB RAM on the laptop so I suspect that this happens for all GOG users, but most simply don't notice because they're on better machines / don't play for hours on end. Simple restart fixes it, but it's supremely annoying having to preemptively restart every couple of hours or so. Playing AE .79 borderless with SSE Display Tweaks.
Post edited March 18, 2025 by Isewein
avatar
baronofdoom.547: Is anyone else having a memory leak issue with the GOG version of Skyrim? It's version 1.6.1179. I use mods but I did a fresh, unmodded installation and tested it and it still does it. This doesn't happen with the Steam version of Skyrim, it's version 1.6.1170. I am using an 8GB GTX 1080 and I can quickly fill up my VRAM by fast travelling several times. When it's maxed out, it starts filling up my system RAM, which is 32GB total. The game at one point had roughly 16GB of it filled up. I let Bethesda know and they just said thanks for the feedback. Just curious if anyone else has noticed this.
avatar
LoRezJez: The problem appears to be with the 1.6.1179.0.8 SkyrimSE executable file that is in the 0.1.3905696 GOG version - that is the only offline installer available - and is the latest of the two versions that is available through GOG Galaxy.

According to the UESP, the only change that was made for the 1.6.1179 version was to change the version number to differentiate the GOG version from the Steam one.

However, clearly something went wrong and introduced this memory leak.

Because, if you install GOG Galaxy and roll back to the only other available version (0.0.3895161), you will get an exe with the 1.6.1170.0.8 version number. And no memory leak. You can then take a copy of that SkyrimSE.exe file and copy it into an installation using the offline 0.1.3905696 installer, and you will also get the game with no memory leak.

The timestamps on the files that get changed by the update show a few additional changes - one of which is clearly shown by a change to the file size (HearthFires.esm from 3885KB to 3886KB). Since there is no changelog we cannot know what has changed - so we have the choice to use all of the older files that changed between 0.0.3895161 and 0.1.3905696, or just the exe.

The main point is that the exe is where the memory leak is, and replacing it with the older one will fix it.
Is GOG aware of this problem?
Post edited March 18, 2025 by SpellSword
Also on laptop with 8GB ram, often get a silent CTD while playing, but almost always if I quit, the program refuses to finish closing, and have to close from task manager / error popup instead. Not sure how to confirm that it's virtual memory at fault, but suspect that's the culprit as there's little extra room on the hard drive. Tried setting a specific value for virtual memory rather than allowing windows to manage, but that didn't seem to help this problem any and just made other odd things happen.
I just notified the problem to the GOG support. Hopefully GOG will fix it ...( everyone affected should contact them too for the issue to be fixed quickly)
Post edited 3 days ago by wcdeadpool