PC Fix the memory leaks!

[General Lee]

In A16.4 I had issues with memory leaks, but it's MUCH worse in A17 experimentals. I used to be able to run the game for hours before running low on memory, but the memory leaks are worse than ever with each update. Now I can barely run the game 30 minutes without having the restart the game. I'm only running 8GB of RAM, but players shouldn't be required to have 16GB just to avoid crashing every hour or less. This is something that has been affecting the game for years now, and it's only getting worse with each subsequent patch.

I'm sure TFP are aware of this, since it's nothing new, but it's time to at least make a statement or something. Love the game, but y'all have got to do something about the memory leaks. I'm not running much of anything in the background, only using about 1.5GB when not gaming, and it's not like I'm running the game using high settings. Could we at least get a statement regarding the memory leak issues?

 

[Katitof]

Either go and make a bug report or stop playing experimental - experimental is SUPPOSED to be bug ridden unoptimized pain fest.

Do NOT play experimental if you just want to play, wait for stable.

 

[meganoth]

As a bug report your information is surely valuable, this is the first time I have seen this mentioned for A17 (but I didn't follow the bug report thread lately). If you post a proper bug report there is a good chance they can replicate it and you might get an answer like "confirmed - we forwarded the bug" from the internal testers. I hope that is what you are after really, feedback that they know about it.

How a statement from TFP would help you in any other way than artifically boosting your self-esteem because you made them apologize for bugs IN AN EA GAME is a mystery to me though.

PS: I know at least one person who plays with 8G who has no problems with A17 to play 5 hours without restarting. There must be some special circumstances to trigger these memory leaks.

Did you restart or are you playing a game from b199 or b208? If the latter, check your console (F1) for errors. And start a new game in b221 to see if it isn't just a problem because of an old save.

 

[LuckyStar]

Either go and make a bug report or stop playing experimental - experimental is SUPPOSED to be bug ridden unoptimized pain fest.
Do NOT play experimental if you just want to play, wait for stable.

 

[General Lee]

Either go and make a bug report or stop playing experimental - experimental is SUPPOSED to be bug ridden unoptimized pain fest.
Do NOT play experimental if you just want to play, wait for stable.

This is a problem that's been around since before A17 experimentals. This was also an issue in A16.4 stable, it's just that it's much worse now. I don't think they are interested in bug reports for A16 builds anymore, lol.

As a bug report your information is surely valuable, this is the first time I have seen this mentioned for A17 (but I didn't follow the bug report thread lately). If you post a proper bug report there is a good chance they can replicate it and you might get an answer like "confirmed - we forwarded the bug" from the internal testers. I hope that is what you are after really, feedback that they know about it.
How a statement from TFP would help you in any other way than artifically boosting your self-esteem because you made them apologize for bugs IN AN EA GAME is a mystery to me though.

PS: I know at least one person who plays with 8G who has no problems with A17 to play 5 hours without restarting. There must be some special circumstances to trigger these memory leaks.

Did you restart or are you playing a game from b199 or b208? If the latter, check your console (F1) for errors. And start a new game in b221 to see if it isn't just a problem because of an old save.

My self-esteem has nothing to do with this. Not sure what you're getting at. I'm complaining about something that's been an issue since A16. Haven't seen anyone mentioning how much worse it is in A17, and haven't had time to fill out a bug report today.

Why you're applauding someone's post who didn't even bother reading the one he responded to, I have no idea. How many times do I have to say it, this isn't something new. The problem has been around for a long time, and they aren't interested in bug reports from previous alphas. Try to keep up.

 

[General Lee]

You know what, nvm. I won't bother bringing up issues any further. Y'all have fun chastising people for pointing out problems. BTW, I was in the middle of filling out a bug report when I lost power earlier today. Maybe that's why I didn't turn one in after posting this thread. Next time, if you're not going to be helpful, don't bother replying.

Mods, go ahead and lock this thread pls.

 

[LuckyStar]

You know what, nvm. I won't bother bringing up issues any further. Y'all have fun chastising people for pointing out problems. BTW, I was in the middle of filling out a bug report when I lost power earlier today. Maybe that's why I didn't turn one in after posting this thread. Next time, if you're not going to be helpful, don't bother replying.
Mods, go ahead and lock this thread pls.

Sorry you didn't get the response you were hoping for.

My feelings on the matter is that it's far too early to report this.

If stable comes out and there are still leaks then yes, that would be a bug worth reporting.

[in the bug section.]

You didn't do that though did you?

You created a rant thread about it.

And you're upset people are rolling their eyes at your post?

Having said that, you're right, I was a little rude with my post.

It's nice to see people care enough about the game to want to see positive changes.

Hopefully if you have some good ideas in the future this won't deter you from posting.

:smile-new:

 

[General Lee]

Sorry you didn't get the response you were hoping for.
My feelings on the matter is that it's far too early to report this.

If stable comes out and there are still leaks then yes, that would be a bug worth reporting.

[in the bug section.]

You didn't do that though did you?

You created a rant thread about it.

And you're upset people are rolling their eyes at your post?

Having said that, you're right, I was a little rude with my post.

It's nice to see people care enough about the game to want to see positive changes.

Hopefully if you have some good ideas in the future this won't deter you from posting.

:smile-new:

Tried posting a bug report earlier, but like I said, I lost power before I could submit it. You didn't even bother reading that part either, did you? Not really worried about it now, not worth the response I got just bringing the subject up.

 

[LuckyStar]

Tried posting a bug report earlier, but like I said, I lost power before I could submit it. You didn't even bother reading that part either, did you? Not really worried about it now, not worth the response I got just bringing the subject up.

Surely you're better than this.

 

[General Lee]

Surely you're better than this.

Mods close or delete this thread. It's apparently a waste of time. Nobody gives a ♥♥♥♥ about a problem that's been around for years since a few people don't seem to have it.

Maybe if the problem doesn't affect you, you shouldn't be ♥♥♥♥ting in the thread...

 

[PPanda0421]

Sorry you didn't get the response you were hoping for.
My feelings on the matter is that it's far too early to report this.

If stable comes out and there are still leaks then yes, that would be a bug worth reporting.

[in the bug section.]

You didn't do that though did you?

You created a rant thread about it.

And you're upset people are rolling their eyes at your post?

Having said that, you're right, I was a little rude with my post.

It's nice to see people care enough about the game to want to see positive changes.

Hopefully if you have some good ideas in the future this won't deter you from posting.

:smile-new:

No it is not far too early to report this. Memory leaks are a serious issue in software development and especially game programming.

Yeah, of course the OP can create a bug report but that's for developers to review. But bringing it up in a different thread might be helpful to users who can discuss the issue/scenarios (perhaps even help the developers pinpoint the leak) without clogging up the bug report thread.

 

[Pizzalicious]

There's been memory leaks in this game for awhile now. Dont worry, "theyll fix it when they goto optimization phase after the game goes live" when's that gonna be? 2025?

 

[LuckyStar]

No it is not far too early to report this. Memory leaks are a serious issue in software development and especially game programming.Yeah, of course the OP can create a bug report but that's for developers to review. But bringing it up in a different thread might be helpful to users who can discuss the issue/scenarios (perhaps even help the developers pinpoint the leak) without clogging up the bug report thread.

Let me rephrase that.

It's too early to start a rant thread about memory leaks.

Reporting bugs as they come out is always helpful.

Does that clarify things?

There's been memory leaks in this game for awhile now. Dont worry, "theyll fix it when they goto optimization phase after the game goes live" when's that gonna be? 2025?

We can't know the work schedule of TFP.

Multiplayer has some game-breaking bugs that won't be fixed anytime soon.

[MM said it's such a huge project that it would take the entire team and thus would be the last thing they work on before release.]

Look, I get that bugs are annoying but TFP has a list of priorities and I doubt they are they same as yours or mine.

We just need a little patience....... okay a lot of patience.

 

[Jugginator]

There's been memory leaks in this game for awhile now. Dont worry, "theyll fix it when they goto optimization phase after the game goes live" when's that gonna be? 2025?

Optimization phase is for Beta typically. You can't do much optimization if you're going to release a bunch of balancing/changes/content that will break the optimization you just did. You can, but doesn't make sense.

 

[LuckyStar]

Optimization phase is for Beta typically. You can't do much optimization if you're going to release a bunch of balancing/changes/content that will break the optimization you just did. You can, but doesn't make sense.

THANK YOU.

That's what I thought too.

Beta is where you dig in and tackle optimization.

 

[Cadamier]

Well... Donno about a memory leak... Don't ever remember having one with 7D2D. I did however notice (albeit I didn't check before) but my GPU is now running towards its 4GB max! And that's even after hours upon hours of playing!

 

[PPanda0421]

THANK YOU.
That's what I thought too.

Beta is where you dig in and tackle optimization.

In general it's best to fix memory leaks early on or it'll be more difficult to find them as the software gets bigger and bigger (eg. adding more features). In addition, the software might have been designed in a certain way and if the fix to memory leaks requires change(s) in design you'll have serious problems in the late stages of development.

IMO any memory leaks should be fixed right away in any stage where you find them so that testing during that stage will be smooth.

 

[LuckyStar]

In general it's best to fix memory leaks early on or it'll be more difficult to find them as the software gets bigger and bigger (eg. adding more features). In addition, the software might have been designed in a certain way and if the fix to memory leaks requires change(s) in design you'll have serious problems in the late stages of development.
IMO any memory leaks should be fixed right away in any stage where you find them so that testing during that stage will be smooth.

Okay not only do I agree with you but so does TFP.

They have been fixing memory leaks as they go.

[At least the patch notes say so.]

I think part of the problem [and I have nothing to back this up] may be the Unity update.

I only say this because other developers are having a difficult time adjusting as well.

Someone even mentioned a game rolling back to Unity 2017 because they just couldn't make it work.

Maybe that's what's going on here?

Major leaks should, like you say, be stomped out quickly.

That's easier said than done, however.

Also... minor leaks, if they are managed by the garbage collector and aren't too serious, can wait a little.

 

[Jugginator]

Yeah, converting to the Unty engine wasn't an easy task for them, why it took so long. They have been fixing memory leaks, indeed, they;re better off than others (like Rust...). Honestly I don't see any memory leak issues unless playing on a large server, there are some serious leakage there. Playing co-op with another person doesn't seem to do it either unless a crash happens. I've heard of people running out of ram with 32GB in the early alpha days of Rust, and I'm not running bad with 8GB on this game. Hell, SWTOR has worse memory leaking and it's a AAA game (although it's complete garbage atm). They're doing fine. There is a trick you can do... I think this will work just the same on Windows 10 to clear out garbage on your ram. Right click desktop, create new shortcut. Add this to the target:

%windir%\System32\rundll32.exe advapi32.dll,ProcessIdleTasks

Name it whatever you want. It will do nothing on your screen, as it's just doing a ram clear which happens in less than a second typically. May need to run as Admin.

(read two posts down for a 64-bit version)

 

[LuckyStar]

Yeah, converting to the Unty engine wasn't an easy task for them, why it took so long. They have been fixing memory leaks, indeed, they;re better off than others (like Rust...). Honestly I don't see any memory leak issues unless playing on a large server, there are some serious leakage there. Playing co-op with another person doesn't seem to do it either unless a crash happens. I've heard of people running out of ram with 32GB in the early alpha days of Rust, and I'm not running bad with 8GB on this game. Hell, SWTOR has worse memory leaking and it's a AAA game (although it's complete garbage atm). They're doing fine. There is a trick you can do... I think this will work just the same on Windows 10 to clear out garbage on your ram. Right click desktop, create new shortcut. Add this to the target:

%windir%\System32\rundll32.exe advapi32.dll,ProcessIdleTasks

Name it whatever you want. It will do nothing on your screen, as it's just doing a ram clear which happens in less than a second typically. May need to run as Admin.

Yeah that's helpful!

It's not a permanent solution but while TFP is busy optimizing and tweaking and such, we'll just have to come up with our own work-arounds.

Thanks for that.