Re: Out of video memory trying to allocate a rendering ressource CRASH-4090-24GVRAM

Product: STAR WARS Jedi: Survivor
Platform:Steam-PC
Summarize your bug The game leaks memory
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? It's easy to reproduce: - Set the page file to a static amount that is way higher than should ever be used (6-8 GB?) - Watch performance monitor + task manager GPU panel and see memory usage and page file size creep up until the entire system crashes (not just the game) - Set page file to be automatically handled by Windows and restart PC - Play the game and watch performance monitor + task manager again; you will see video memory / page file usage creep up but when the limit is nearly reached, more page file space will be allocated. Eventually it could reach a gargantuan size. Notice that performance monitor usage appears steady because it is using the same percentage of available memory, but the total memory is increasing due to paging, thus the total used memory is also continuously increasing.
What happens when the bug occurs? If the page file has a static size, the entire system crashes and must be hard reset. If the page file is dynamically allocated, the game may crash but it takes much longer due to the continuous enlargement of the page file. If the limit is reached anyway, the game crashes but otherwise the PC is functional.
What do you expect to see? I expect the game to correctly allocate/deallocate memory like every other game on the market.

‌

All performance metrics are normal except video memory, which steadily climbs while the game is running until the limit is reached, never deallocating memory. Graphics drivers are up to date, tried rolling back a version which made no difference. DxDiag reports no issues. Windows (and therefore DX12) up to date. Regenerated DX cache at AppData/Local/ which made no difference. No leaking issue in any other game ever, including other DX12 games and Jedi Fallen Order which run perfectly.

Since paged memory can be used by the graphics drivers, bloating the page file to sickening levels allows the game to run for a while (more available memory means the leak takes longer to max out memory and require a restart). This isn't an option for anyone using an HDD (as performance is abysmal) or anyone who doesn't have a lot of free space on their drive to allocate to a monstrous page file.

I honestly wouldn't be surprised if most of the people who have played with minimal issues just don't realize that by default the page file will dynamically allocate with no limit, whereby they would never realize there was a problem until they ran out of free disk space to feed the page file, or in the event that a sufficiently large request for memory was made between page file allocation intervals. For anyone with plenty of extra space, this could take hours to occur. Changing texture quality changes the amount of time it takes to crash, likely since lower quality textures take up less space, resulting in smaller allocation increments.

Take a look around EA forums and Steam discussions and you will see this issue manifest on a wide array of graphics cards from different generations and architectures, some from NVIDIA and some from AMD.

This issue is therefore clearly hardware agnostic. It is not a matter of insufficient video memory if a 4090 with 24 GB is having the same exact problem. My GTX 1080ti has 11 GB which is far beyond what is required for the game to run. Everything performs impeccably until the timebomb explodes.

This is a huge issue, and expecting people to have infinite disk space to allow indefinite paging to compensate for a leak is simply unacceptable. Not to mention that "workaround" isn't 100% reliable even for those who can do it.

Just in case you are curious, my CPU is a Ryzen 5 3600x with 16 GB DDR4 @ 3200 MHz. CPU/RAM performance is unremarkable. Not that this has anything to do with a video memory leak, but I figured I would mention it anyway.

I'll be happy to provide some screenshots of the leak in action if for some reason you decide that's better than reproducing it yourselves.

Product: STAR WARS Jedi: Survivor
Platform:PC (Steam)
Summarize your bug I can play for about 15-30 minutes on low settings, every I can turn off is off. and resolution is below 1080p
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? Start game and watch the vram usage continue to climb till the out of vram message pops up.
What happens when the bug occurs? The game crashes
What do you expect to see?   I expect to be able to just play the game for more than 15 minutes at a time

Processor Ryzen 5 5600X 6-Core

RAM 16 GB DDR4
GPU AMD Radeon RX 6700XT


Now since the new patch, where the game would spike at 15 GB of RAM being used before the patch, now at just loading the game it jumps to 15.5 GB of RAM used before crashing

@Sl1nkman  I don't work for EA and don't have any access to the developers or QV, but I'd love to see those screenshots.  I have a few of my own showing that what you describe wasn't happening on my system as of patch 1.04 at least.  I'm running a 9700K and RTX 2070 (8 GB VRAM), and although RAM and VRAM usage are high, they're quite stable.  And so is the game for the most part, having crashed only once and frozen a handful of times.

The graphs below represent hwinfo logs created while playing on Koboh on patch 1.02 (red) and 1.04 (green), and while RAM and page file use are higher in the latter, they don't keep increasing.  I wasn't doing anything special, just running around collecting loot and and admiring the view and slashing things with a lightsaber.

This is not at all to cast doubt on what you're seeing.  Your description would explain why some people are seeing instability despite having hardware that exceeds the game's requirements, and I'm wondering what the difference is between your system and the others affected on the one hand and mine on the other.

If you'd like to look over the full hwinfo logs, let me know and I'll zip up a few for you.  I haven't tested on patch 1.05 yet, having finished the game a few days ago, but I can do that too.

@AkiraWarhiet  One thing I notice in your dxdiag is that your computer's page file is almost entirely used, and 18 GB of page file in use is extremely high if you're not running anything demanding at the time of the dxdiag.  Do you use gaming-related apps while playing, for example Razer software or an RGB controller?  It would be helpful to know whether shutting down absolutely everything other than JS and the EA App and Steam makes a difference.

Additionally, have you read the post immediately above yours?  I can't tell you whether this is what's happening on your computer without looking at the results of some hardware monitoring, e.g. an hwinfo log, but it's a plausible explanation.  Even more so considering how in use your page file is and how little free space you have on C.  By the way, it would be good to clear another ~15 GB, so 25 total free, just for the overall health of your computer.

If you'd like to upload an hwinfo log for people to look at, or you can analyze one yourself and post the results, that would be interesting as well.  Check the post above this one for mine, which don't show at all the same effects as you or the previous post describe, but hopefully provide a useful data point.

Even closing all apps, within seconds of the game loading after the main menu the not enough vram message comes up.

Also I did clean up the c drive, still no change

@AkiraWarhiet  Are you willing to upload an hwinfo log to show what's happening on your computer?  In case you're not familiar, download hwinfo (it's free) from here:

https://www.hwinfo.com/download/

You don't need to install anything; just choose the Portable version, unzip it, and launch it from Downloads or wherever you like.  If you do want the full installer, be sure to click the button for hwinfo itself, not for lansweeper.

Restart your computer, open hwinfo (but nothing else), choose Sensors Only, and click the button that's a sheet of paper with a + to start logging.  Save the log file to your desktop for easy access.  Wait five minutes, then launch Jedi Survivor and let it go until it crashes.  Don't alt-tab out of the game or run any other programs, aside from the EA App of course, while you're testing.  When you're done, click the same button to stop the logging.

Please upload the log to the third-party filesharing site of your choice (Google Drive, Dropbox, etc.) and link it for me.  Either leave it in .csv format or, if you're going to use OneDrive, create a .zip file, and don't open the log before uploading it, or else my log reader might not be able to interpret it.

hopefullly i did it right

will say I did get to play for a couple minutes before it crashed this time


https://drive.google.com/file/d/1BTCX14uY6zvUeRYOM2XGDvx9kFjabhLe/view?usp=sharing

Gigabyte Amd Radeon rx 6800 master is also vram leaking in game with no fix so far look forward to playing but one day maybe 

Produkt :  STAR WARS Jedi: Survivor (Version bzw Patch Status unbekannt, wird das automatisch geupdatet?) 
Plattform : PC (EA App) 
Fassen Sie Ihren Fehler zusammen.Ich habe bis vor ca. 1,5 Wochen (Mitte Oktober) auf hohen Einstellungen in WQHD Auflösung ohne Probleme gespielt. Etwa 20 Stunden Spielzeit, irgendwo auf Koboh aktuell. War im Urlaub und versuche seit 2 Tagen weiterzuspielen. In meinen bisherigen Einstellungen stürzt das Spiel nach einigen Sekunden ab, VRAM ist nicht ausreichend laut Fehlermeldung. Auf den niedrigsten Einstellungen kann etwa 10 Minuten spielen, alles, was ich ausschalten kann, ist ausgeschaltet.
Wie oft tritt der Fehler auf?  Jedes Mal (100 %)
Schritte: Wie können wir den Fehler selbst finden?  Radeon Status sagt mir eine Auslastung des Arbeitsspeichers von 15,5 GB. 
Was passiert, wenn der Fehler auftritt?  Das Spiel stürzt ab. Schwarzer Bildschirm. Hin und wieder Fehlermeldung. 
Was erwartest du zu sehen?   Perfekt funktionierendes Spiel. 

Prozessor  Ryzen 5 5600 6-Core

RAM  16 GB DDR4
GPU  AMD Radeon RX 6800 16GB Vram


Entweder wurde das Spiel kürzlich gepatcht (wo finde ich die Patch Version des Spiels?) und der Fehler tritt dadurch auf oder der Fehler rührt von der aktuellen Adrenalin Version. Ich habe das Spiel schon mehrmals repariert in der EA app, komplett neu runter geladen und installiert, Adrenalin neu installiert und die Vorgängerversion benutzt. Nichts funktioniert. 

https://steamcommunity.com/app/1774580/discussions/0/3826415752021965635/ 

This is still a serious problem, on Koboh my VRAM quickly (as within an hour) gets up to the limit of my 4090, 21-22GB indicated in MSI Afterburner, and the game chugs heavily, with severe hitching, even though the FPS is at 75-80 (7680x2160, DLSS FG enabled, DLSS: Quality), disabling RT improves the FPS by about 10 and maybe cuts the hitching in half but doesn't eliminate it. What an absolutely gorgeous game, it's such a shame that it has this problem, I don't have another game in my entire library of over 100 games across multiple launchers that does this. That there is no continued communication from the devs is extremely concerning, are they working on this? $70 for this title, this is completely unacceptable. I purchased the game at a great discount on EA otherwise I would be extremely angry to have sunk over 2 hours into this only to find that it's borderline unplayable once you make it to Koboh outside of the refund window on top tier hardware.

I've got exactly that insane problem. Even setting page file size to 40-60GB doesn't resolve it. Koboh with so much open areas is the worst. There is one long sequence between save points when one have to destroy three or four "clanks" over thermal "chimney" to fly over them and get boost to get the higher locations but it is undoable on my hardware because of that crap with high VRAM and consequently Virtual Memory usage. ☹️