Jump to content

Crash Receiving Memory Allocation Error

#8776 Known Issue

144 replies to this topic

Poll: Crash Receiving Memory Allocation Error (458 member(s) have cast votes)

Are you experiencing this issue?

  1. Voted Yes (407 votes [88.86%] - View)

    Percentage of vote: 88.86%

  2. No (51 votes [11.14%] - View)

    Percentage of vote: 11.14%

How often are you experiencing this issue?

  1. Never (0%) (49 votes [10.70%] - View)

    Percentage of vote: 10.70%

  2. Rarely (1-19%) (42 votes [9.17%] - View)

    Percentage of vote: 9.17%

  3. Occasionally (20-39%) (63 votes [13.76%] - View)

    Percentage of vote: 13.76%

  4. Sometimes (40-59%) (57 votes [12.45%] - View)

    Percentage of vote: 12.45%

  5. Frequently (60-79%) (82 votes [17.90%] - View)

    Percentage of vote: 17.90%

  6. Voted Often (80-99%) (74 votes [16.16%] - View)

    Percentage of vote: 16.16%

  7. Always (100%) (91 votes [19.87%] - View)

    Percentage of vote: 19.87%

Vote Guests cannot vote

#81 Alka Seltzer

    Rookie

  • 3 posts

Posted 05 February 2014 - 01:44 PM

Greetings,

i've been playing this game for about a month now and never had this error prior to UI 2.0. I have done roughly 20 games after the patch that introduced it and pretty much exactly every third game i'm getting kicked out by the memory bug while my Mech's powering up. I tried using the repair tool yesterday and again after today's hotfix, however this didn't help. I also lowered the effects to medium level to no avail, but didn't experiment with graphic settings any more than this. I'm on a 32-bit Windows btw. Well, hopefully the issues with the new UI can be resolved soon.

Best regards,


Alka Seltzer.

#82 GryHwk

    Member

  • PipPipPip
  • The Hunter
  • The Hunter
  • 65 posts

Posted 05 February 2014 - 04:47 PM

Well, I have tried everything my not so techy mind can do..... but yet another online game that has updated me from playing. Shame, I have thrown money and time into this one, enjoyed playing a lot. Thinking ya'll need to "Patch Back" to the old version and rework your "2.0" I'm just one voice that you could do without, you'll get others that will have the tech and powerful puter's that will be able to play..... Just thought I would get my 2 cents in before I'm just another customer that gets left behind in oblivian, while you march on into the world of growing businesses that could care less......... I thank you for the little time I had to play the game.... I'll just pull out my old windows 98 computer and play Mechwarrior3 until i melt the cd......

#83 martino2k6

    Member

  • PipPipPip
  • Philanthropist
  • 96 posts
  • LocationEurope

Posted 06 February 2014 - 01:45 PM

This has started happening to me ever since UI 2.0 came out. This error will popup after a game has been found, or just during the scoreboard or initial moments of a game. Insanely infuriating, as it happens every one or three games.

Repair tool didn't help.
Reinstalling didn't help.
Changing graphics to lowest didn't help.
Checked my RAM and all is fine.

Windows 8.1 64-bit.

#84 Volt Corsair

    Member

  • PipPipPipPipPipPip
  • The Clan Cat
  • The Clan Cat
  • 203 posts
  • LocationOutpost, Periphery (HPG down)

Posted 06 February 2014 - 04:31 PM

So a common theme here is that UI2.0is what's bringing the problem to the surface. I can attest to the fact that since CB, despite my machine being under the minimum requirements, still ran the game. It got better to the point where I was getting almost consistent 20-30 fps. Then the UI update. Now I am guaranteed to hit it every single time I launch in any form. This can only point me towards the direction of something in the code being altered for the worse at the last moment because UI2.0 was rushed in incomplete. Hopefully this gets fixed in the very near future.

Laptop
Windows 7 Home Premium 32-bit OS
Radeon 6400 series
AMD E-350 Processor 1.60GHz, no overclocking due to bad cooling
2GB of RAM, 1.6 usable

#85 Khan Wotan

    Rookie

  • Civil Servant
  • Civil Servant
  • 3 posts

Posted 06 February 2014 - 07:01 PM

This was about 1 in 3 matches since UI2.0 release, however today, its every match with this message of memory allocation, even with all settings set to Low. With UI1.5 this was not occuring. Was there regression testing done with UI2.0 before release since this was a serious issue in the past? Please fix this ASAP, ty.


***UPDATE*** 2/7/14
Removing and reinstalling the game whcih I read someone else did to fix the issue did help me a little. One crash in 3 games again. A reinstallation of a Game or an App should not be the fix when a new patch or update comes out but in this case it did help me. We shall see what happens in a few days time if I end up crashing each game again.

Edited by Khan Wotan, 07 February 2014 - 07:35 AM.


#86 chaas

    Member

  • PipPipPipPipPip
  • The Clamps
  • The Clamps
  • 111 posts

Posted 06 February 2014 - 08:31 PM

View PostKhan Wotan, on 06 February 2014 - 07:01 PM, said:

This was about 1 in 3 matches since UI2.0 release, however today, its every match with this message of memory allocation, even with all settings set to Low. With UI1.5 this was not occuring. Was there regression testing done with UI2.0 before release since this was a serious issue in the past? Please fix this ASAP, ty.


I'm running into the same issue as this, running a machine that's just barely better than minimum specs*. Had this problem way back in the beta, where I could at least get 4 games in before the game crashed and burned. Before the "Hot Fix" patch, I was getting through two games and crashing as the third one loaded. After the hot fix, I got through the third game and then due to other responsibilities, closed down and left. Since then, I've attempted on multiple occasions at different times of the day to join a game. During the load-in process, my Memory Usage exceeds 1.25 GB and then boom goes the dynamite.

This version of the UI clearlyhas issues, and it's infuriating to see them openly neglected while the powers that be rush production. A number of these issues were brought up in the public test feedbacks, yet are now listed as known issues. It's very clearly unfinished and was pushed through to appease the masses begging for progress. While it's a step forward, it's also about six steps backwards. We're looking at a laundry list of problems that points to a product that should have been finished before entering production. Deadlines be damned, it's bad business to push a broken product! That decision would have cost someone their job in most institutions. Business be damned, it's insulting to the product's consumers. I genuinely hope someone learned a valuable lesson from this gaffe.

I'd be ranting less if I could actually shoot something right now. Don't you dare take that as an apology.


*Athlon 2 X4 630, Radeon HD 5750, 4GB DDR 1333, XP 32-Bit, DX9.

#87 Elric Tchernovkov

    Member

  • PipPip
  • Ace Of Spades
  • Ace Of Spades
  • 28 posts
  • LocationOdins' Eye

Posted 06 February 2014 - 09:51 PM

Before Ui 2.0 I would see this error only if I played for more than 6 hours straight. or approx. 30 -35 games in a row. After UI 2.0 I see this every 1-3 matches, have never actually completed 3 matches in a row. I have tried the repair tool. I have run Memtest on my RAM. Nothing seems to work. I have changed video cards ( turns out my onboard was actually better than my old nvidia 9500 GT) Nothing seems to work. I refuse to go lower than medium settings cause then I am just a sitting duck for the jaegers and BJ's who snipe from all the way accross the map. I have an i5 processor with an onboard HD 4600 graphics processor, 4gb of DDR3 ram and have upped my virtual memory to 8GB. Nothing works. Please fix this.

#88 MikeFreeman

    Rookie

  • Shredder
  • 6 posts

Posted 06 February 2014 - 11:33 PM

I got the same issue. Before UI 2.0 it happens every now and then, but with textures set to low it was nearly fine. BUT now it happens EVERY game.... It shows me the map loading screen and right before I would see the team overview it crashes with some kind of CryEngine Error "*** Memory allocation for 5592540 bytes failed ***".

I ran Win7 32-bit with 4gb RAM.

@Devs & Support: Is this issue under investigation?

#89 Gauss Master

    Rookie

  • The Widow Maker
  • The Widow Maker
  • 7 posts
  • LocationMissouri

Posted 07 February 2014 - 02:50 AM

I only receive a memory error and crash every time HGN Manifold comes up in map rotation, I crash to desktop every time. all other maps and features are working a little better since hotfix after patch. Pre hotfix, it was crap.

#90 Peace2U

    Member

  • PipPipPipPipPipPip
  • 368 posts

Posted 07 February 2014 - 03:22 AM

Hello fellow Mechwarriors.
Sorry I can't add any additional technical input on this issue other than I never had a game crash before this patch.
At this time, I cannot even enter a match before the memory allocation error occurs and closes the game.
My spec's are fairly low, but still exceed the game requirements.
Also, I have the graphics set to low as others have suggested.
I feel for you guys who are burning premium time, waiting for the fix.
If this is, in fact, a wide-spread issue, is it possible to 'roll back' to the pre-pached state so we can continue playing while the developers work out the bugs?

Note: the new interface is cool looking in some ways, but more difficult to use in others.
Also, some information available in the previous interface is no longer available (XP earned for mechs you no longer own)???

Peace All

#91 BjornAreStolen

    Member

  • Pip
  • 13 posts

Posted 07 February 2014 - 04:53 AM

First of all, thanks for a free online game in one of my favourite settings. This is the first time I have ever played an online-game. This is allso my first post in theese forums, and I just have a question; does anybody who have anything to say about MWO actually reply to threads like this one, or is it just a vent for frusterated people?

I'd really like to know what's beeing done about this sort of stuff, not a lenghty in-detail report, but just some quick words, keeping us up to date if you're years away from mending it, months, weeks or hours :angry: If you tell us that our computers are crap and we need to update our hardware, that's allso OK, as long as we actually are informed :)

I'm btw allso one of those who played flawlessly until the patch that came 5.february. Now my game crash'es once every 4th game :/

#92 Khan Wotan

    Rookie

  • Civil Servant
  • Civil Servant
  • 3 posts

Posted 07 February 2014 - 07:24 AM

A clean reinstallation of the game has helped me so that I am crashing every 3rd game instead of every game. While reinstalling the game has helped me be able to play atleast a few matches, it is not a solution for those countries that have a download limit as it can become expensive to do for each release. Please address this issue ASAP, ty.

Edited by Khan Wotan, 07 February 2014 - 07:33 AM.


#93 BL0WHARD

    Rookie

  • The 1 Percent
  • 4 posts

Posted 07 February 2014 - 08:15 AM

This used to happen 1-30 games. I had to keep Textures to Low.

Now it is 1-6 games with everything set to low. Any Custom setting for video or anything at Medium causes it to occur every time.

Win8 32 bit, plenty o' graphics and mem

#94 USMC Iceman

    Member

  • PipPipPip
  • FP Veteran - Beta 1
  • FP Veteran - Beta 1
  • 80 posts
  • LocationUSA

Posted 07 February 2014 - 10:41 AM

I keep getting an issue after the 2nd patch after 2.0 where I can't use my Friends list with out the game locking up and crashing. Anyone else? :P I even deleted the game and did a clean install. Same issue.

#95 chaas

    Member

  • PipPipPipPipPip
  • The Clamps
  • The Clamps
  • 111 posts

Posted 07 February 2014 - 10:52 AM

View PostBjornAreStolen, on 07 February 2014 - 04:53 AM, said:

First of all, thanks for a free online game in one of my favourite settings. This is the first time I have ever played an online-game. This is allso my first post in theese forums, and I just have a question; does anybody who have anything to say about MWO actually reply to threads like this one, or is it just a vent for frusterated people?

I'd really like to know what's beeing done about this sort of stuff, not a lenghty in-detail report, but just some quick words, keeping us up to date if you're years away from mending it, months, weeks or hours :P If you tell us that our computers are crap and we need to update our hardware, that's allso OK, as long as we actually are informed :huh:

I'm btw allso one of those who played flawlessly until the patch that came 5.february. Now my game crash'es once every 4th game :/


In this case, the revival of this thread is largely for venting purposes. I can't imagine PGI is unaware of the issue, and I'm sure we'll hear the usual "We're working diligently to ... " presser at some point in the near future. I'm quite discouraged at this point.

And of course in the meantime I went to reinstall my copy of NHL 08 to pass the time, only to find that it's unplayable as well. Seems one of the early load lines in that game tries to connect to a server that EA has since repurposed, so I can't even get to the main menu. Granted the game's 6 years old, but I can still play MechWarrior 4: Mercenaries just fine. Conclusion: EA wants more of my money than PGI.

What I'm saying is my rage has yet to subside. Many, many expletives have been spoken.

#96 TW 996

    Member

  • Pip
  • Survivor
  • 17 posts
  • LocationGermany, Osnabrück

Posted 08 February 2014 - 05:45 AM

I can´t play...
i have to use the medium video options but my computer is to slow... so i have a extreamly slide show (unplayable)
bevore the patch it works awsome.i have to wait for the new patch. at he moment its ipossilble to play the game :)
bye bye

#97 valt901

    Member

  • PipPipPip
  • Rage
  • Rage
  • 92 posts

Posted 08 February 2014 - 11:03 AM

I never had this problem before UI 2.0. My settings are set to high and i have been crashing every two or three games. Ran the repair tool last night and it crashed on my third game. This is something you would expect in closed beta not when the game is in full open mode. It is fast becomming unplayable.

#98 Elric Tchernovkov

    Member

  • PipPip
  • Ace Of Spades
  • Ace Of Spades
  • 28 posts
  • LocationOdins' Eye

Posted 08 February 2014 - 09:38 PM

Way back at the beginning of this thread there is a flag at the top saying " Known issue" Niko Snow used to respond to these and I've seen 1 other Dev post on this thread. From everything i've read you need two things; First upgrade your system to 64 bit. And check/replace your RAM. I am moving to 64 bit on whatevr day my new DVD drive comes in ( for some reason Windows 8 installed at 32 bit) hopefully by wednesday I can tell you if this worked or not. If that doesn't work I will be getting new/ different RAM. Will advise if these work unless IGP releases a hotfix on tuesday. Also I finally got through a match with my D-DC, was first match completed with that mech since the patch. My other mechs were all getting through 1 to 3 matches before crash. I figured out yesterday that the D-DC crashes more often than the others. As far as LRM boats are concerned I don't think it matters. My SHD doesn't have LRM's and it crashes just as often as the rest. I tried deleting the shader cache file and that didn't help any. Seriously thinking this is a 32 bit OS bug or this game has fried my RAM in some way that memtest doesn't detect.

#99 martino2k6

    Member

  • PipPipPip
  • Philanthropist
  • 96 posts
  • LocationEurope

Posted 09 February 2014 - 07:04 AM

View Postprinceelric, on 08 February 2014 - 09:38 PM, said:

Way back at the beginning of this thread there is a flag at the top saying " Known issue" Niko Snow used to respond to these and I've seen 1 other Dev post on this thread. From everything i've read you need two things; First upgrade your system to 64 bit. And check/replace your RAM. I am moving to 64 bit on whatevr day my new DVD drive comes in ( for some reason Windows 8 installed at 32 bit) hopefully by wednesday I can tell you if this worked or not. If that doesn't work I will be getting new/ different RAM. Will advise if these work unless IGP releases a hotfix on tuesday. Also I finally got through a match with my D-DC, was first match completed with that mech since the patch. My other mechs were all getting through 1 to 3 matches before crash. I figured out yesterday that the D-DC crashes more often than the others. As far as LRM boats are concerned I don't think it matters. My SHD doesn't have LRM's and it crashes just as often as the rest. I tried deleting the shader cache file and that didn't help any. Seriously thinking this is a 32 bit OS bug or this game has fried my RAM in some way that memtest doesn't detect.

You will notice in this thread that this is also happening to users on 64-bit machines. Also a game can't really fry your RAM. Something like a very strenuous stress test could, but it's still very very unlikely. The error is happening due to a memory leak (someone forgot to use free after malloc), which results in the system being starved of memory and the game crashing because there is no memory left for it to allocate. This is on PGI's plate, and the sooner they get to it the better.

Edited by martino2k6, 09 February 2014 - 07:05 AM.


#100 The Incredible Microbe

    Member

  • Pip
  • 18 posts

Posted 09 February 2014 - 01:38 PM

I want my Premium-Time back... as i crash every 3rd to 5th game due to this stupid memory-allocation-failure... i have to start the game again, and again, and again... this is frustrating! It worked fine for me BEFORE this stupid UI 2.0 came...





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users