FIX THE MEMORY LEAK ALREADY.

[inhearts]

Let's see, Rockstar. You've released the most anticipated port i've ever seen. You told us you'll do your best, and for the most part you did. For most people it is flawless. However, the memory leak issue is getting serious and a nice big chunk of the people that bought your game are experiencing the problem. I hope you're already on it, and I hope you don't end up like the MKX release on PC, which left players no game time for three days because the download issues made it unplayable. Please, please, please, do something and do it fast, I want to be able to play.

The main issue for people unfamiliar:

A memory leak is when a game gradually starts chewing up more and more RAM until it crashes. After about 40 minutes of gametime once, I checked task manager and found it using up 2,500,000 memory. Within the first minute the game is flawlessly running smooth-as-butter, but after around 30 minutes the stuttering and lags kick in.

It's not this paging ♥♥♥♥, that's been debunked countless times. Monitor RAM usage, stop being blind because it's clear as day that it's a memory leak.

[Valazor]

another perfect example that age doesn't matter. don't call annoying people on the internet "12 year olds" .... 36 year olds can be the same amount of braindead.

[Munnky]

Publicado originalmente por Fuse404:

Publicado originalmente por twitch.tv/munnky78:

Nice try, im 36. Im just appauled at squeakers and those with the mental aptitude of a squeaker who just whine and ♥♥♥♥♥. Like it will really get them anywhere? And on the Steam forums of all places. I am sure the devs know what a cesspool this place is. If you can act adult and request a fix with out sounding like a spoiled self intitled ♥♥♥♥ it will get much better responses from those that can make the changes. Like Immunitys post. Well constructred, possitive and informed. Not just some rubbish being spewed out of nerd rage because there game doesn't work. Also I am getting the same issues, but luckily I upgraded to 16GB RAM and so it hasnt affected the game yet.

While there are more polite ways to express it, I wouldn't call asking for a game one purchased to actually work "entitled", no matter how the request is phrased.

Asking and ♥♥♥♥♥♥♥♥ about it is two different things. It all about how you present yourself.

[Munnky]

Publicado originalmente por banedejong7000:

another perfect example that age doesn't matter. don't call annoying people on the internet "12 year olds" .... 36 year olds can be the same amount of braindead.

You completely missed the point of my post.

[⭕⃤ BIPPO]

Please, ignore the preteen trolls. They will eventually get tired and go play minecraft yelling at their friends via micro. Just ignore them!

Publicado originalmente por banedejong7000:

another perfect example that age doesn't matter. don't call annoying people on the internet "12 year olds" .... 36 year olds can be the same amount of braindead.

indeed lol.

[nuna]

Publicado originalmente por banedejong7000:

another perfect example that age doesn't matter. don't call annoying people on the internet "12 year olds" .... 36 year olds can be the same amount of braindead.

[(void*)0]

Publicado originalmente por Fuse404:

Publicado originalmente por return 0:

It's not. Feel free to embarrass yourself explaining why you incorrectly think it is.

So why did the PC version take so much longer if it was being developed in parallel with the console verisons?

I know Max Payne 3 was developed in parallel, and GTA V PC was handled by the same team, but did they ever say GTA V PC was being developed in parallel?

Yes: http://www.vg247.com/2015/04/13/gta-5-pc-development/
There are also build logs from at least 2012.

The PC team was much smaller as R*'s primary focus was next-gen consoles. It was originally slated to release along with them and well it's easy to guess it was still a mess.

[Squall Leonhart]

Publicado originalmente por Shamanalah:

Publicado originalmente por OBIPPO:

As I said, I don't know if this is a memory leak or not, I just said that the problem exists and it's not some collective illusion like some turds are saying here. Also, I don't care about your uneducated opinion or your PC. You're lucky I'm in the mood to respond to trolls and clowns right now, but that won't happen again so you can shut the ♥♥♥♥ up, get lost and never come back to this topic.

I'm a dev student with an IT level 1 knowledge... I know more about PC than you do.

GTA V has no memory leak. Most people that has problem with their RAM have 8gig and up and think they can allocate memory to their PC because "it's my PC" well no, your PC is managing his memory usage and if GTA V has optimisation isssue then the memory will start going ballistic because GTA V is using it and not properly freeing it.

IF THERE IS A MEMORY LEAK. Launching GTA V would simply void out your RAM until it is freed by the OS (until you restart basically)

So if a memory leak WAS happening, you would lose actual physical memory usage each time you launch GTA V, and it doesn't happen.

False:

For what you are saying to occur, the programming would have to be done on the metal level,

Memory management on modern operating systems (Since Win9x infact) is done virtually, the API and the Game do not get to touch registers directly and as such cannot remain forever in memory after having been loaded.

Under a virtual memory managed operating system, processes request a memory space of their own to operate in or request for it to increase by , with the Kernel itself performing the virtual <> physical mapping,

To put it in terms the majority will understand, the process Asks for space, and this space is provided in a Bubble, whatever the application does in this bubble affects only this bubble, this bubble can grow and shrink (under normal conditions) and have rarely used portions paged out to disk, unmapped, and freed as should be normal behavior of an application.

When the application exits, or is terminated forcefully, this bubble is destroyed by the OS, all of the data within the bubble is removed and the kernel free's the physical memory and any data paged to disk is also removed.


Application Memory Leaks are contained to the User Address Space, and are fully removed from memory once the offending process is terminated.

Driver memory leaks are contained to the Kernel Address Space and depending on whether they are high or low level drivers, may or may not be removed from memory once the driver is stopped.

Publicado originalmente por Shamanalah:

What's a var?
What's an int?
What's a static private class?
What's the benefit of going single thread vs multi thread?
What's the dfference between stack and heap?
What's a deleagate?

If you can answer this then let's talk programming!!!! otherwise just don't tell me GTA V has memory leak, cause you can't answer those simple questions

I''ve field experience with programming and IT2 and a number of other IT fields that im not certified in

And I'm saying you are talking out your ass.


The issue is a textbook example of a modern Memory leak (your textbook seems stuck back in the PCDOS days), it can be reproduced under the games safe mode and affects both graphical and non graphical data,

At 800x600 with all settings off, this game should not be eating 5GB's of GPU Commit. (3GB Vram + 2GB dumped to page), and yet, it does.

[Valazor]

ah yes , the internet. where EVERYONE is an IT specialist.

[Squall Leonhart]

Publicado originalmente por banedejong7000:

ah yes , the internet. where EVERYONE is an IT specialist.

I'm Squall from the Visual Boy Advance, XBCD, X360CE, NrageInput, Project64, eduke32..etc, its a long list of projects.

I just felt the need to call Shamanalah on his bs.

oh, for those interested,x360ce fully works with GTA5 now :)

[⭕⃤ BIPPO]

Publicado originalmente por banedejong7000:

ah yes , the internet. where EVERYONE is an IT specialist.

True lol ^^^^^^^^^^^^

[ZombieHunter]

This game has all the evidence of a memory leak b/c it CTD's about once every hour to hour and a half. It seems to happen more after gun battles, etc which might be due to spawning in objects and then failing to remove them from memory which eventually crashes.

However, I have 16GB of RAM and even if it leaked quite a bit that would take quite some time to use up on a 64-bit system. But it also depends on whether or not GTA is a 64-bit or 32-bit app. If it's 32-bit without large address aware then it can only use 4GB else it can use all of my RAM. This might explain the timing of my crashes, etc,

If you want to see RAM usage then use the Process Explorer from SysInternals. Windows Task Manager is not a good tool to use for this.

A memory leak is simple. Allocate memory from the system and fail to de-allocate it. Or in C terms malloc without free and in C++ new without delete. However, given that C++ 11 has new constructs to assist with memory management like shared_ptr, weak_ptr, etc. most C++ programs will rarely use raw pointers so leaks will be less frequent. I'm not sure if games would use these or not and b/c I haven't been using C++ 11 much I don't know the overhead (if any) for using these constructs. They are from Boost and TR1 but not sure how they were implemented in MSVS.

Keep in mind even though this has the appearance of a memory leak it doesn't mean it has one. You would have to track memory usage over time and then find out what actions in the game caused it to jump. But in the end you really need to see the code to verify what is happening. Its very easy to be an armchair developer but code is complex and it could be a number of different things.

Best bet is to wait for a patch. Rockstar did a fantastic job on the port in general so I hesitate to go off half-informed and start making assumptions. The team that ported the game knew what they were doing but since it is the PC and there are a million different configurations out there its usually impossible to squash every issue before release. Give them time.

[Defektiv]

Every indication seems to point to a memory leak for my crashes as well. I have no other problems with the game and the only other games I own that crash like this are EA titles with known memory management issues. The client always detects the crash and sends me back into game, but doesn't recover unsaved progress, which is kind of bit game-breaking. The only way I can combat this is to keep staring at a memory monitoring application while I'm playing and make sure I save whenever things start looking sketchy. That's not really how I expected to be playing a title I had to pay full price for.. twice.

[Squall Leonhart]

Publicado originalmente por falcon_x:

This game has all the evidence of a memory leak b/c it CTD's about once every hour to hour and a half. It seems to happen more after gun battles, etc which might be due to spawning in objects and then failing to remove them from memory which eventually crashes.

However, I have 16GB of RAM and even if it leaked quite a bit that would take quite some time to use up on a 64-bit system. But it also depends on whether or not GTA is a 64-bit or 32-bit app. If it's 32-bit without large address aware then it can only use 4GB else it can use all of my RAM. This might explain the timing of my crashes, etc,

If you want to see RAM usage then use the Process Explorer from SysInternals. Windows Task Manager is not a good tool to use for this.

A memory leak is simple. Allocate memory from the system and fail to de-allocate it. Or in C terms malloc without free and in C++ new without delete. However, given that C++ 11 has new constructs to assist with memory management like shared_ptr, weak_ptr, etc. most C++ programs will rarely use raw pointers so leaks will be less frequent. I'm not sure if games would use these or not and b/c I haven't been using C++ 11 much I don't know the overhead (if any) for using these constructs. They are from Boost and TR1 but not sure how they were implemented in MSVS.

Keep in mind even though this has the appearance of a memory leak it doesn't mean it has one. You would have to track memory usage over time and then find out what actions in the game caused it to jump. But in the end you really need to see the code to verify what is happening. Its very easy to be an armchair developer but code is complex and it could be a number of different things.

Best bet is to wait for a patch. Rockstar did a fantastic job on the port in general so I hesitate to go off half-informed and start making assumptions. The team that ported the game knew what they were doing but since it is the PC and there are a million different configurations out there its usually impossible to squash every issue before release. Give them time.

The game is 64bit,
Because the game excessively maps VRAM and fails to free old data, it spills out into and consumes additional Commit Charge which leads to even more physical memory and page file usage then it would if it was just a process memory leak.

[Fuse]

Publicado originalmente por return 0:

Publicado originalmente por Fuse404:

So why did the PC version take so much longer if it was being developed in parallel with the console verisons?

I know Max Payne 3 was developed in parallel, and GTA V PC was handled by the same team, but did they ever say GTA V PC was being developed in parallel?

Yes: http://www.vg247.com/2015/04/13/gta-5-pc-development/
There are also build logs from at least 2012.

The PC team was much smaller as R*'s primary focus was next-gen consoles. It was originally slated to release along with them and well it's easy to guess it was still a mess.

Publicado originalmente por return 0:

Publicado originalmente por Fuse404:

So why did the PC version take so much longer if it was being developed in parallel with the console verisons?

I know Max Payne 3 was developed in parallel, and GTA V PC was handled by the same team, but did they ever say GTA V PC was being developed in parallel?

Yes: http://www.vg247.com/2015/04/13/gta-5-pc-development/
There are also build logs from at least 2012.

The PC team was much smaller as R*'s primary focus was next-gen consoles. It was originally slated to release along with them and well it's easy to guess it was still a mess.

Cool. Thanks for the link. Most of my hunting had turned up hearsay.

[ZombieHunter]

Because the game excessively maps VRAM and fails to free old data, it spills out into and consumes additional Commit Charge which leads to even more physical memory and page file usage then it would if it was just a process memory leak.

I suspected it was due to vertex buffers, shaders, or textures not being released but didn't want to say anything b/c honestly I have no proof. But what you said makes sense.