search

ValveSoftware / Source-1-Games

Source 1 based games such as TF2 and Counter-Strike: Source
647 stars 75 forks source link

[L4D1] Out of Memory attempted allocation size: 0 crash bug (2023) #4674

Closed JayBoom closed 1 year ago

JayBoom commented 1 year ago

wkcMTkl

This is happening probably 70% of the time when the chapter/campaign changes.

Reply I gave to steam support:

Game crashed again. I have no addons or mods or any workshop items.

It seems to be a common issue I have found on Github (Source game bugs), Steam discussion for the game and reddit and more. It crashed again today and got this error (see attached)

All that happened was the chapter change in a campaign, it always happens on a chapter change or a campaign finish or campaign change. In this case of the screenshot it was a few seconds after we closed the saferoom door and were about to load into the next chapter it crashed.

This is also happening on friends machine's as well, so the specs don't seem to be the issue. I know some people online mentioned multicore rendering being turned on makes it more common which i do have turned on.

Although apparently it is a very easy fix as L4D1 is a 32bit game so you just have to code in for it to use 4gb of RAM instead of 2gb, which some community members have created an update which fixed this, so if you could please just get any developer on the Valve team to push an update to fix this it would be amazing.

Also see attached bug thread as well as the attached comment showing the error dates back to 2019.

A community developer described it as "it consists of updating and changing the ram consumption from 2GB to 4GB in left4dead.exe."

Thanks Support team :) If just the right person is notified this could be pushed in an update and easily fixed.

kisak-valve commented 1 year ago

Hello @JayBoom, this issue is already being tracked in various issue reports like #2646 / #3350 / #3446. Closing as a duplicate.

JayBoom commented 1 year ago

Hello @JayBoom, this issue is already being tracked in various issue reports like #2646 / #3350 / #3446. Closing as a duplicate.

How come this is not fixed yet then if it has been reported 3 other times at least and traces back to 2019 and is such a simple fix that even a community dev was able to patch it within a day?

Sorry if that sounds rude but just curious thats all.