Doom Eternal crashes with 495.46 on high VRAM usage

Graphics / Linux Linux
1

Running Doom Eternal using Wine/Proton on 495.46 with a low proportionate VRAM usage (5230 / 8192 MB as reported ingame) works just fine, no crashes or performance issues.

However, as soon as one adjust the graphic settings so it uses more VRAM (7603 / 8192 MB) the game will crash when trying to load a game map with “Failed to allocate video memory”;

img-2022-01-08-144838

Game Settings: Multipaste (2 files) - img-2022-01-08-143917.png, img-2022-01-08-143931.png

When one lowers the VRAM usage slightly this can also occur while playing instead of on load.

nvidia-bug-report.log.gz (546.4 KB)

2 Likes
2

According to the Proton GitHub Issue thread this issue was introduced with 495 and is not present on 470: Doom Eternal (782330) · Issue #3773 · ValveSoftware/Proton · GitHub

3

This is still an issue on 510.47.03.

4

This is still an issue on 510.54

5

any workarounds ? 510 is pretty f_ed

1 Like
6

Still an issue with version 510.60.02.

1 Like
7

It seems like this issue may be fixed in driver version 515.43.04. See the comment string found here.

8

bump.

Still an issue for me with 525.105.17. VRAM Usage on ultra nightmare on my 3070 instantly has the VRAM usage locked to 7.9/8.0GB with nothing to spare. FPS is meh but other processes slow to a halt and am unable to open anything even marginally GPU accelerated at this point.

9

Bumping again. Doom Eternal at 1440p Ultra Nightmare with DLSS, Ray tracing off, still seems to be using more vram than expected. Computer also usually ends up completely locking up as the vram gets filled.

10

Hi @faz
Please confirm if you have tested it with recently released driver 550.78.
If yes, please share nvidia bug report from repro state once doom eternal crashes.

12

nvidia-bug-report.log.gz (949.0 KB)

Here is the bug report log after the crash of Doom Eternal.

13

Thanks for sharing the logs, shall share the update once I get update from engineering team.

1 Like
14

Here is another example, Spider-Man remastered on 555 drivers working for a few minutes before completely freezing with a vram leak. I can run these exact settings perfectly fine on windows, what is the issue here? Attempted proton 8 and proton 9 (experimental), both having this issue. Leading me to believe its nvidia issue again sadly.

nvidia-bug-report.log.gz (417.6 KB)

15

update: still occurring on new 555.52.04 drivers. Tested open kernel modules, and closed kernel modules with and without gsp firmware.

1 Like
16

update: still occuring on new 555.58.02 drivers. Tested open kernel modules, and closed kernel modules with and without gsp firmware. @amrits , any help? Unable to play some games due to this issue, and I’ve done all I can to share logs with you. Spiderman remastered freezes after a few minutes with a vram leak (does not occur on windows), and doom-eternal uses much more VRAM than initially expected (also tested on windows, does not use nearly as much vram there)

1 Like
17

another update - still happening on the latest rounds of 560 beta drivers. @amrits, any chance you were able to get an update from the engineering team?

1 Like
18

I can 100% confirm this. As soon as VRAM reaches limit everything slows down at least to 50% of the beginning performance.
It seems no cleanup of any vram inclduded stuff is happening which results into just growing growing growing until VRAM is completely full.

19

Looks similar to this issue : Non-existent shared VRAM on NVIDIA Linux drivers

1 Like
20

hey amrits, any update? Seems to still not be fixed with the 565 upgrade. Just as bad as before if not worse. I shared further info here however got no reply: 565 release feedback & discussion - #33 by faz