You are not logged in.
Every time I try to load up the campaign, I crash with a *OUT OF MEMORY* window that pops up with a bunch of buttons that all have assert in them. Is this a map problem, or is my computer just a piece of shit?
It ran the original L4D fine...
If it helps, it makes a .mdmp called "(failed)left4dead_assert_201006 5190030_2.mdmp"
I also get an out of memory crash but mine is different. The error message reads:
***** OUT OF MEMORY! attempted allocation size: 3969044 ****
I usually get this on the 4th level/Lumberyard. I have 4G RAM and run all other source games just fine.
Just thought you would want to know about the error. Love the campaign otherwise.
Yeah, this kinda sucks because I can't play the campaign at all.
I get this issue a lot in l4d1 - it has little or nothing to do with the campaign (although I get it more in customs like this one then stock campaigns).
It has nothing to do with your ram.. I have 8 gigs, and run out of memory with the exact same message.
I've filed a support ticket on it about 6 months ago.. I suggest you do the same. Maybe valve will actually fix it.
If it is due to the campaign, it is only because of how detailed it is (theres more entities in this campaign then most any other).
Last edited by Dirka_Dirka (2010-06-06 21:01:12)
Alright, I'm pretty sure that we can conclude that it's NOT the graphics...I had it on the lowest possible setting, and I still crashed.
Sorry for the double post, but it's not just part of IHM, it just happened when I loaded Crash Course, to. This is a serious bug.
This is very weird. And it happens like that? Without any warning or anything special happening in game?
for me it can happen at any time (it happend when i got stuck on map 2 - RIGHT AFTER getting free, and it happened after the crane crescendo.. although i was able to play by ignoring the error until map change).. it also happens at map change frequently usually around maps 3-4.
for comparison.. a friend was playin with me tonight and we both have win7 64bit, but he has intel/nvidia and i have amd/ati. his hardware is also older then mine.. he didnt crash once, so maybe its an ati issue.
oh boy, lucky me. 2 in 1 campaign last night.
first time was loading up map 3 (the earliest i have gotten it yet), and then it happened a 2nd time right after i killed the 2nd tank in the finale. no escape for me.. the credits were rolling by the time i kicked myself and rejoined.
i also just re-upped my support ticket with valve on this damned issue.. i suggest everyone else who is crashing create their own.
At this point, I'm not sure they can do something. It seems entirely hardware-related and memory errors are the toughest bitches to understand. You'd need a memory dump and a good amount of knowledge just to understand what caused it and still, you wouldn't have any solution.
well i forgot i had done something oh so long ago.. and it seems that is what has been causing my crashing.
just played a whole campaign w.o a crash, when before i couldnt complete one.
solution for me:
i REMOVED -heapsize from my command line settings.
not only that, but i wasnt even using the highest value (which is 2097151 - just under 2 gigs), i was using 1572864 (1.5gigs).
increasing the heapsize to 2097151 actually caused me to crash sooner.
oh ya, this kind of issue i wouldnt blame on the mappers, unless it happened at the exact same place/time/spot/condition. thats why i opened an issue with valve way back when (probably a month after i added that damned option to the command line).
oddly enough it was the mdumps i got from my initial install and crash issues that led to the solution (i didnt get any dumps from these errors).
Last edited by Dirka_Dirka (2010-06-10 16:09:30)
I was already trying to figure out why your pc with "more than required specs" was becoming a can of tuna for the engine (cause that's the symptome of free edicts error allong with a mapper who places too many brushes/models in his map).
I had loading probs too when I had 2 gb of ram and the game loved to stutter at area portals especially in no mercy 2.
Last edited by CosmicD (2010-06-10 18:48:52)
back to the ops posting..
thats a FAILED mdump file.. it will most likely be 0 size. the game tried to make a dump but couldn't.. i had several of those myself. they were probably failed because of the size. the couple of dumps the game actually managed to create on these crashes were > 10 megs.
if anyone else is using -heapsize, remove it.. if your not using -heapsize, try adding it to your command line