Bad Allocation Error #4258

[badger77]

Similar ingame effects to the smart memory heap error I had in 1.30 - sound goes into repetative loop - game lags heavy, freezes and CTD's.

Lasted about 2 mins ingame before crash.

Log as follows

1

4278198017

1844

52

3515903376

0

3765269347

1964685095

0

GL Vendor: NVIDIA Corporation|Renderer: GeForce GTX 260/PCI/SSE2|C++ Exception: class std::bad_alloc bad allocation at address 751AB727

------------

W7 64 bit

I7

GTX 260

6GB Ram

Xonar D2X

-----------------------

Just experienced it again next spawn - Possibly sound related. clicking noise / gun noise goes into perma loop.

Game lagged but didn't crash - Lag about 4 - 8 seconds long before moving again.

No packet loss - lowish ping.

Edited June 7, 2010 by badger77

[badger77]

OK it seems I can replicate / Force the error in the same way Smart heap errors hit me in 1.30.

If I turn sound to software rather than hardware then it seems to work. (Still selecting The Asus Xonar DX2 so not using primary sound driver)

Not ideal since I have a new soundcard and software not great. So it seems sound related and yes I have every up to date driver, chipset etc and don't have any sound issues elsewhere in games or OS / Applications.

[badger77]

Spoke too soon.

Error is still prevalent and it seems to be around large explosions and mortars combined with mg fire (possibly AI / tank).

One of them starts looping continually then get huge lag and freeze ups.

Never had CTD or crash with software selected as sound so thats an improvement. As you can see from last log no packet loss

Actual bytes per second sent 592

Actual bytes per second received 7792

Message bytes per second sent 624

Message bytes per second resent 0

Message bytes per second queued 624

Message bytes per second processed 7349

Message bytes per second ignored 912

Total bytes sent 264973

Total bytes received 1877941

Total message bytes sent 141299

Total message bytes resent 0

Total message bytes queued 141299

Total message bytes received 1745334

Total message bytes ignored 2749

Messages in send buffer, by priority 0,0,0,0

Bytes in send buffer, by priority 0,0,0,0

Messages in resend buffer 0

Bytes in resend buffer 0

Current packetloss 0%

Average packetloss 0%

Elapsed connection time in seconds 280

[GOPHUR]

I'm going to try and replicate this.

[badger77]

Thanks Gophur - Hard to work out. I turned V Sync off and now run off software on sound card and only had it once more.

Again a looping sound of MG - Game froze, no dump - haad to force quit - sound loop kept going after game quit.

ON ANOTHER note. Just tried to switch personas from French to British

Bad allocation error

1

4278198017

2122

36

3515903375

0

3765269347

1990571815

1990571815

94582227

94565598

94530786

94525852

94514429

7737153

7740017

7740215

8616575

0

GL Vendor: NVIDIA Corporation|Renderer: GeForce GTX 260/PCI/SSE2|C++ Exception: class std::bad_alloc bad allocation at address 76A5B727

[AHWULF]

This is a variant of the "out of memory" error.

++ Exception: class std::bad_alloc bad allocation

[badger77]

Yes - I did notice I was running in vista compatibility mode from last version lol.

So taking that off has helped my FPS and my GPU to push a little more.

So I put hardware back on in sounds. Spawned in and within 20 seconds got a crash. I'm convinced it's an interaction with my new sound card (Xonhar D2X)

My previous XFI card had no issues on 1.30 but this one did

NEW Crash log from this crash backs up your out of memory theory Ahwulf.

Remember my rig has 6GB and is using about 49% max when running the game. Card has 896MB

1

4278198017

3423

34

3515903379

0

3765269347

1999681319

0

GL Vendor: NVIDIA Corporation|Renderer: GeForce GTX 260/PCI/SSE2|C++ Exception: class std::runtime_error Out of memory at address 7730B727

[AHWULF]

Try the Low Memory option, it seems to change loading enough that some of the ctds go away.

I'm thinking the error may not be running OUT of memory, but something stomping ON memory messing up the heap.

[GOPHUR]

Compatibility mode...huh.

In 1.30 the executables are ww2_x86.exe and ww2_sse2.exe. They would have had compatibility mode on for mouse fixes in Vista and Win7.

They don't exist in 1.31. We now use ww2.exe for the game executable. In 1.30 it was used as a launcher for one of the other .exe's but having compatibility mode on it would do nothing that I can see.

Definately want all compatibility modes turned off on ww2.exe.

[badger77]

Yeah as an update I turned off compatibility mode and it made little difference BUT did allow the GPU to use more resources and hence my FPS is a buit better.

It was stuck on 30% but now hits 60% odd.

I then ran BE as Administrator and SO FAR that simple little change has resulted in no crashes and I am runnign on hardware.

So for now case closed. On W7 run as administrator with no compatibility mode of you forgot to turn it off from last version

Thanks guys. It's little things like this that can help multiple people and sort out odd issues.