Halo CE memory leak thread / fixed july 12th

[Abbe]

343 you MUST hotfix the memory leak in halo ce, people paid for this product and it's non functional at the moment. I know iam shouting into a void but i must make it heard.
Proof: https://www.youtube.com/watch?v=uB21J-qShG8

*edit* it's been a long wait but the update day is finally confirmed for july 12th, let's hope the update fixes the issue and see you guys in game.
*edit 2* it's been confirmed fixed.

[Abbe]

Originally posted by IceBreaker:

Originally posted by Abbe:

we really don't need anymore threads because in the end it really does not matter, 343 already knew about this since december and decided to do frick all about it.

Not arguing that point, but I'd rather try and find a solution than complain about it more. If this is related to an AMD driver, then its not really in 343's hands either; its in AMD's.

Most threads on this issue aren't presenting any data to try and figure out what exactly is happening, even if it does come down to 'well the game is broken'.

Believe me, I'm not impressed either, but I'm more interested in a solution or a work-around - just want to play Halo.

not trying to be mean but did you read the other posts ? the update back in december for mcc broke support for amd gpus, it's not amd, it's 343 the only solution you have is either 1: wait for update or 2: replace amd gpu with nvidia gpu, someone posted about limiting ram could potentially fix it with some 3rd party software but honestly at that point i'd rather just play another game and it's not even a tried fix, you can try it if you want but do check how large your page file gets if you do try it.

[Sulzway Firth]

Just chiming in to say that I was able to play through the entire game with no problems at all once I installed the patch from before the December patch. It's still a wonky way to have to play the game and achievements don't work in it, but I thought I'd go ahead and confirm that yeah, absolutely no problems during the entire playthrough when using the identical settings on the previous patch, now that I've completed it. Current patch was totally unplayable though.

Also, I've seen a few posts saying that the memory leak also effects Halo 2 Anniversary - interestingly enough, I'm not having issues with that one so far. The ram usage does seem a little high for my liking, but it never completely spirals out of control like Halo CEA does. So I'm not sure where that complaint is coming from or if this just means the issue is even more complicated than we thought.

[IceBreaker]

Currently testing with friends pc.

Rolling back to adrenalin 22.1.2 has so far seemed to resolved the memory leak issue.

However, it would previously crash due to memory choke out after about an hour and, despite no longer leaking, Halo CE did hard freeze after a similar amount of time.

Second test is in progress.

Edit: two notes with this

- GPU in question is a 6600xt
- Performance is massively more stable on the older driver

[IceBreaker]

After an 85~ minute session I was able to complete Silent Cartographer without technical issues. Memory peaked at about 1.98GB

If anyone would like to confirm my solution and has this issue with an AMD GPU
* Remove current display drivers with DDU
* Install Adrenalin 22.1.2 from here
https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-1-2

I theorize that an AMD driver from November/December has been the culprit, if more people can confirm this as a solution. Previous installed driver was 22.11.2 or 22.11.3

Rolling forward to latest (23.3.2) did NOT solve the issue, only rolling backwards did.

Don't want to jump to conclusions, but I could also imagine that no one has informed AMD of this being an issue with their driver either.

I'm not going to test any further since its working for me, but next steps would be to check drivers closer to november/december (22.10.3)

I also highly recommend starting a new thread for this.

[Sulzway Firth]

Originally posted by IceBreaker:

After an 85~ minute session I was able to complete Silent Cartographer without technical issues. Memory peaked at about 1.98GB

If anyone would like to confirm my solution and has this issue with an AMD GPU
* Remove current display drivers with DDU
* Install Adrenalin 22.1.2 from here
https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-1-2

I theorize that an AMD driver from November/December has been the culprit, if more people can confirm this as a solution. Previous installed driver was 22.11.2 or 22.11.3

Rolling forward to latest (23.3.2) did NOT solve the issue, only rolling backwards did.

Don't want to jump to conclusions, but I could also imagine that no one has informed AMD of this being an issue with their driver either.

I'm not going to test any further since its working for me, but next steps would be to check drivers closer to november/december (22.10.3)

I also highly recommend starting a new thread for this.

I found this interesting and I was still awake so I figured, what the heck, I'll give it a shot.

Definitely works. I'm back on the current patch for Halo CEA, using the drivers that you linked, and sure enough, things seem to be running a lot smoother. Ram usage was perfectly stable the entire time.

I only played through the entire first mission in my test run, but I can confirm that the numbers are way different from when I played that mission with the current patch with the current drivers - if I hung around in the first mission long enough I could get crashes, but with this old driver, no such thing.

I suspect the numbers will differ in Halo 2 as well, but I'll have to test that later, it's getting to be past my bedtime.

[Abbe]

Originally posted by IceBreaker:

After an 85~ minute session I was able to complete Silent Cartographer without technical issues. Memory peaked at about 1.98GB

If anyone would like to confirm my solution and has this issue with an AMD GPU
* Remove current display drivers with DDU
* Install Adrenalin 22.1.2 from here
https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-1-2

I theorize that an AMD driver from November/December has been the culprit, if more people can confirm this as a solution. Previous installed driver was 22.11.2 or 22.11.3

Rolling forward to latest (23.3.2) did NOT solve the issue, only rolling backwards did.

Don't want to jump to conclusions, but I could also imagine that no one has informed AMD of this being an issue with their driver either.

I'm not going to test any further since its working for me, but next steps would be to check drivers closer to november/december (22.10.3)

I also highly recommend starting a new thread for this.

nice find, maybe the dates being so close a driver fault was mistaken as an mcc fault, however this does not explain why 343 has not commented on this as they have stated they are aware of the issue, if it truly was an amd fault surely 343 would have given amd a notice (remember microsoft is one of amd's biggest partners) and commented publicly that it's not in their hands, iam 99% sure there is more to this than just drivers.

[IceBreaker]

Originally posted by Abbe:

nice find, maybe the dates being so close a driver fault was mistaken as an mcc fault, however this does not explain why 343 has not commented on this as they have stated they are aware of the issue, if it truly was an amd fault surely 343 would have given amd a notice (remember microsoft is one of amd's biggest partners) and commented publicly that it's not in their hands, iam 99% sure there is more to this than just drivers.

Only more people testing it will highlight the real issue. So far had a 3 hour session without memory issues on the older driver.

I'm not privy to the details of how partnership communications work.

Maybe 343 didn't get enough information to determine that it was strictly an AMD related issue, maybe the MCC team was pulled away to work on other things - I don't know how they operate and I won't pretend to.

But if this turns out to be a good solution to the problem, then I'm sure the information will reach the right people in time.

Until then, hopefully more people can simply play Halo CE - that's about all I care about.

[Abbe]

Originally posted by IceBreaker:

Originally posted by Abbe:

nice find, maybe the dates being so close a driver fault was mistaken as an mcc fault, however this does not explain why 343 has not commented on this as they have stated they are aware of the issue, if it truly was an amd fault surely 343 would have given amd a notice (remember microsoft is one of amd's biggest partners) and commented publicly that it's not in their hands, iam 99% sure there is more to this than just drivers.

Only more people testing it will highlight the real issue. So far had a 3 hour session without memory issues on the older driver.

I'm not privy to the details of how partnership communications work.

Maybe 343 didn't get enough information to determine that it was strictly an AMD related issue, maybe the MCC team was pulled away to work on other things - I don't know how they operate and I won't pretend to.

But if this turns out to be a good solution to the problem, then I'm sure the information will reach the right people in time.

Until then, hopefully more people can simply play Halo CE - that's about all I care about.

i get what you mean but it should be noted that downgrading drivers is not recommended and we should discourage it as people not knowing better could end up doing irreverisble harm to their windows install by using DDU, do not downgrade drivers unless you know what you are doing and even then i still don't recommend it as amd drivers are currently bugged when ticking "clean install" and could end up making your windows inoperable with windows installing drivers when it notices you don't have any installed as you are installing new ones. if you are reading this, don't do it. it's not fear mongering, just a warning. even if an old driver works it's not a fix as chances are you will want to play other games that could end up being broken by older driver, it's not worth the hassle and instead of promoting this "fix" we could raise the concern to amd and 343.

[IceBreaker]

Of course, this is an unofficial, temporary fix (if it is one)

yes, submit this information to the proper channels so a proper fix can be made

Until a proper fix happens, this is an option, and its not something to be afraid of - do some reading and understand what you're doing first, but don't be intimidated.

[Abbe]

Originally posted by IceBreaker:

Of course, this is an unofficial, temporary fix (if it is one)

yes, submit this information to the proper channels so a proper fix can be made

Until a proper fix happens, this is an option, and its not something to be afraid of - do some reading and understand what you're doing first, but don't be intimidated.

one singular googling says otherwise, take great caution when doing this.
https://www.digitaltrends.com/computing/amd-driver-windows-crashing-boot-problems/

*edit* iam sure you are a nice person who just want to help but if you don't want to read (which you clearly don't as you misunderstood what was said in the thread) and want do to no research on anything other than swapping drivers and recommending stuff that is absolutely not recommended as you seem to have no clue whatsoever that the drivers despite me telling you can break a windows install as it makes bios changes then i would kindly ask you to make your own thread and go tell people to go screw their systems there instead, i said my piece on the matter.

[Ryan Cook]

Originally posted by SoZetterSulz:

Just chiming in to say that I was able to play through the entire game with no problems at all once I installed the patch from before the December patch. It's still a wonky way to have to play the game and achievements don't work in it, but I thought I'd go ahead and confirm that yeah, absolutely no problems during the entire playthrough when using the identical settings on the previous patch, now that I've completed it. Current patch was totally unplayable though.

Also, I've seen a few posts saying that the memory leak also effects Halo 2 Anniversary - interestingly enough, I'm not having issues with that one so far. The ram usage does seem a little high for my liking, but it never completely spirals out of control like Halo CEA does. So I'm not sure where that complaint is coming from or if this just means the issue is even more complicated than we thought.

I was one of the people that commented halo 2 anniversary as at least for me specifically on Xbox Series X I had several instances of Cairo Station mission freeze in a way where specifically the game would freeze first, then all sounds that were playing or looping would stop, and fade out one by one, not a crash, I had to quit the game manually, happened next if I remember correctly at the start of Delta Halo once too.

This was an issue for me as I chose to play legendary with faster firing weapons skull on making it pretty hard lol, but this lost a little progress every time, has not happened since though and I'm now up to the very end of Delta Halo.

I mentioned it because it was xbox which is amd, and because of saber/game engine similarities maybe, console might be more memory limited.

[Ryan Cook]

I wonder if the cutscene objects being messed up is anything to do with this? Although the only levels affected by that as far as i know are The Pillar of Autumn, and 343 Guilty Spark, this issue appeared very recently in the last december update along with the missing reach enemies on LNoS, and missing in atmosphere frigate cannon tracers on Tip of the Spear.

And I'm not sure how many people noticed but for a short time right after the last update halo 1 missions wouldn't load the next one, you were booted to main menu but that was fixed very quickly, I think it was maybe a week after the December 7th update.

[Abbe]

Originally posted by Ryan Cook:

Originally posted by SoZetterSulz:

Just chiming in to say that I was able to play through the entire game with no problems at all once I installed the patch from before the December patch. It's still a wonky way to have to play the game and achievements don't work in it, but I thought I'd go ahead and confirm that yeah, absolutely no problems during the entire playthrough when using the identical settings on the previous patch, now that I've completed it. Current patch was totally unplayable though.

Also, I've seen a few posts saying that the memory leak also effects Halo 2 Anniversary - interestingly enough, I'm not having issues with that one so far. The ram usage does seem a little high for my liking, but it never completely spirals out of control like Halo CEA does. So I'm not sure where that complaint is coming from or if this just means the issue is even more complicated than we thought.

I was one of the people that commented halo 2 anniversary as at least for me specifically on Xbox Series X I had several instances of Cairo Station mission freeze in a way where specifically the game would freeze first, then all sounds that were playing or looping would stop, and fade out one by one, not a crash, I had to quit the game manually, happened next if I remember correctly at the start of Delta Halo once too.

This was an issue for me as I chose to play legendary with faster firing weapons skull on making it pretty hard lol, but this lost a little progress every time, has not happened since though and I'm now up to the very end of Delta Halo.

I mentioned it because it was xbox which is amd, and because of saber/game engine similarities maybe, console might be more memory limited.

if you have an issue with xbox series x then i can almost gurantee you it has nothing to do with an issue we have on pc on another game, the issue here is driver/343 coding related, xbox does not use drivers as they are only needed on the pc platform because of how hardware can be swapped and customised. besides; speculation on these things is pointless as it is up to 343 to finally acknowledge that mcc exists and fix it.

[Ryan Cook]

Originally posted by Abbe:

Originally posted by Ryan Cook:

I was one of the people that commented halo 2 anniversary as at least for me specifically on Xbox Series X I had several instances of Cairo Station mission freeze in a way where specifically the game would freeze first, then all sounds that were playing or looping would stop, and fade out one by one, not a crash, I had to quit the game manually, happened next if I remember correctly at the start of Delta Halo once too.

This was an issue for me as I chose to play legendary with faster firing weapons skull on making it pretty hard lol, but this lost a little progress every time, has not happened since though and I'm now up to the very end of Delta Halo.

I mentioned it because it was xbox which is amd, and because of saber/game engine similarities maybe, console might be more memory limited.

if you have an issue with xbox series x then i can almost gurantee you it has nothing to do with an issue we have on pc on another game, the issue here is driver/343 coding related, xbox does not use drivers as they are only needed on the pc platform because of how hardware can be swapped and customised. besides; speculation on these things is pointless as it is up to 343 to finally acknowledge that mcc exists and fix it.

Fair enough, I was more so saying though that mcc overall could have errors that reach across from xbox/pc because the game itself may have errors as the last update was messy overall like the anniversary objects being wrong and not lining up with the original graphics in halo 1 that appeared at the same time on December 7th.

But yeah not helping, its better to have evidence and focus on the right places.

[Abbe]

Originally posted by Ryan Cook:

Originally posted by Abbe:

if you have an issue with xbox series x then i can almost gurantee you it has nothing to do with an issue we have on pc on another game, the issue here is driver/343 coding related, xbox does not use drivers as they are only needed on the pc platform because of how hardware can be swapped and customised. besides; speculation on these things is pointless as it is up to 343 to finally acknowledge that mcc exists and fix it.

Fair enough, I was more so saying though that mcc overall could have errors that reach across from xbox/pc because the game itself may have errors as the last update was messy overall like the anniversary objects being wrong and not lining up with the original graphics in halo 1 that appeared at the same time on December 7th.

But yeah not helping, its better to have evidence and focus on the right places.

i appreciate it and yeah i agree, mcc is not in a good state on xbox or steam atm (i own a series x myself), let's just hope they fix most issues on both platforms.