16 replies to this topic

[EvilCow]

After the last patch the ages-old "memory allocation error" has worsened.

Now my game crashes ALWAYS even if it is the first game after launching MWO and doing nothing else but launch.

The error always happens on Terra Therma and Crimson, so on large maps.

System specs: E6600@3.12ghs dual core, 4GB of RAM, WinXP SP2, ATI5870 with latest drivers.

Before someone comes up with redundant suggestions better specify:
1) Repair tool used.
2) Cache cleared.
3) Texture quality set to low.

It would be nice to have an acknowledge about the problem because my PAID premium time is ticking happily.

This is the last part of the errors log:

Quote

<18:43:08> ============================ Loading level mechlab ============================
<18:43:13> [Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/laser_beam_1x4_lop0.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/laser_beam_1x4_lop0.dds]
<18:43:13> [Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/ppc_beam_b.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/ppc_beam_b.dds]
<18:43:13> [Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/ppc_beam_b.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/ppc_beam_b.dds]
<18:43:13> [Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/laser_beam_1x4_lop0.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/laser_beam_1x4_lop0.dds]
<18:43:14> ======== mechlab is loaded in 5.8 sec ========
<18:43:43> [Error] <Flash> Error: GFxLoader failed to open 'Libs/UI/System\../Screens/Assets/UIWebDownloads/DailyStock.jpg' [Libs/UI/System\Main.gfx]
<18:43:43> [Error] <Flash> GFxLoader failed to open "Libs/UI/System\../Screens/Assets/UIWebDownloads/DailyStock.jpg" [Libs/UI/System\Main.gfx]
<18:43:43> [Error] <Flash> Error: GFxLoader failed to open 'Libs/UI/System\../Screens/Assets/UIWebDownloads/Stock.jpg' [Libs/UI/System\Main.gfx]
<18:43:43> [Error] <Flash> GFxLoader failed to open "Libs/UI/System\../Screens/Assets/UIWebDownloads/Stock.jpg" [Libs/UI/System\Main.gfx]
<18:43:48> Material objects/mechs/skins/invasion_a/stormcrow_invasion_a not found during Unregister
<18:43:48> could not free all buffers from CDevBufferMan!
<18:43:48> UnLoadLevel End: 0.3 sec
<18:43:51> Game rules class: Skirmish
<18:43:51> ============================ PrepareLevel lavaworld ============================
<18:43:52> Initializing default materials...
<18:43:58> [Error] Runaway thread
<18:44:01> [Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/forestcolony_clouddome_a.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/forestcolony_clouddome_a.dds]
<18:44:01> [Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/laser_beam_1x4_lop0.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/laser_beam_1x4_lop0.dds]
<18:44:01> [Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/ppc_beam_b.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/ppc_beam_b.dds]
<18:44:17> [Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/laser_beam_1x4_lop1.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/laser_beam_1x4_lop1.dds]
<18:44:17> ======== lavaworld is loaded in 25.8 sec ========
*** Memory allocation for 44698328 bytes failed ****

Edited by EvilCow, 30 August 2014 - 08:55 AM.

[Oderint dum Metuant]

EvilCow, on 30 August 2014 - 08:54 AM, said:

After the last patch the ages-old "memory allocation error" has worsened.

Now my game crashes ALWAYS even if it is the first game after launching MWO and doing nothing else but launch.

The error always happens on Terra Therma and Crimson, so on large maps.

System specs: E6600@3.12ghs dual core, 4GB of RAM, WinXP SP2, ATI5870 with latest drivers.

Before someone comes up with redundant suggestions better specify:
1) Repair tool used.
2) Cache cleared.
3) Texture quality set to low.

It would be nice to have an acknowledge about the problem because my PAID premium time is ticking happily.

This is the last part of the errors log:

Surprised you haven't fixed this yourself

[Deathlike]

This is the only suggestion I can provide you, since the 3GB stuff isn't auto-enabled under WinXP/Vista.

http://dwf.blogs.com...dows-vista.html

[EvilCow]

DV McKenna, on 30 August 2014 - 09:06 AM, said:

Surprised you haven't fixed this yourself

I find surprising that the problem is still here after months. For sure, in my code, I don't let stay even formatting errors.

Deathlike, on 30 August 2014 - 09:11 AM, said:

This is the only suggestion I can provide you, since the 3GB stuff isn't auto-enabled under WinXP/Vista.

http://dwf.blogs.com...dows-vista.html

I will try this but I think the problem is related to texture memory and that is not affected by that switch.

Edited by EvilCow, 30 August 2014 - 09:31 AM.

[Oderint dum Metuant]

EvilCow, on 30 August 2014 - 09:29 AM, said:

I find surprising that the problem is here after months. For sure, In my code I don't let stay even formatting errors.

You should have a race with them

[Deathlike]

TBH, I hate giving the solution that you should just move onto Win7 or better... because that has literally solved my problem on a more long term basis.

[Brizna]

I have Win 7 32 bits and this problem is also present, far worsened since the last patch btw.
Apparently 64 bits with biger acces to memory is the solution and 32 bits OS despite being officially suported by MWO are not actually that much supported.

[EvilCow]

Right, it is not matter of OS version, just available memory, probably also 64bits systems would be affected given enough time for the leak to eat the available space.

[Oderint dum Metuant]

EvilCow, on 31 August 2014 - 02:37 AM, said:

Right, it is not matter of OS version, just available memory, probably also 64bits systems would be affected given enough time for the leak to eat the available space.

I wonder if this is why occasionally i get a close programs due to low memory error in Windows 8.1 (64bit) when my memory surpasses 3GB (8GB system total RAM).
It only occurs during MWO play sessions.

[Idealsuspect]

EvilCow, on 30 August 2014 - 08:54 AM, said:

After the last patch the ages-old "memory allocation error" has worsened.

Now my game crashes ALWAYS even if it is the first game after launching MWO and doing nothing else but launch.

The error always happens on Terra Therma and Crimson, so on large maps.

System specs: E6600@3.12ghs dual core, 4GB of RAM, WinXP SP2, ATI5870 with latest drivers.

Before someone comes up with redundant suggestions better specify:
1) Repair tool used.
2) Cache cleared.
3) Texture quality set to low.

It would be nice to have an acknowledge about the problem because my PAID premium time is ticking happily.

I guess " Faction " feature isnt innocent... since this feature appearsi had to reduce graphic setting for avoid systematic memory error allocation....
Alpine map give a lots of memory allocation error and tourmaline too ... obviously bigs maps yes ...


Well changing OS 32 to 64 is your lone hope it seem now.

Maybe try a rollback with ATI drivers ... " 13-4_xp32_dd_ccc_whql.exe " were good and strong with all sort of games.


Good luck and see you soon on battlefield... o7

Edited by Idealsuspect, 31 August 2014 - 06:12 AM.

[Wolfways]

I used to get the Memory Allocation Error a long time ago but reducing the Textures option in game fixed it, until around the time we got UI2.0 and it returned. Even putting Textures on Low hasn't helped.

I have 32bit Win7.

[Lyoto Machida]

Same issues here...Win XP 4gb RAM.

[EvilCow]

It appears to hit 32bits users regardless if WinXP or Win7.

An upgrade is not an option for me right now because work-related legacy applications, also, upgrading to Win7 would not help anyway apparently.

Could we please have some feedback about this issue?

[M0rpHeu5]

THey told me from support that the devs know of the issue and are looking into it.

[Brizna]

Just for the record: After upgrading to Win7 64 bits the problem is gone (so far). And yes the problem was that bad that I actually spent an evening reinstalling the whole system to get rid of it.

Disclaimer: Of course migration to a new system implies a fresh install of all drivers so there is a chance the problem was there rather in the 64 bits part. That said the chance is slim to say the least, my previous win7 32b system worked flawlesly except for MWO.

Edited by Brizna, 03 September 2014 - 12:33 PM.

[Brizna]

Sorry double post, tried to edit the previous post to add some more info but the text didn't update.

Just for the record I have not experienced a single memory allocation CTD since I updated to 64bits OS. Before I did so I experienced a few before the last patch (aug 26th) and many after it each day.

[EvilCow]

Probably the 64bits OS is just masking the underlying problem, 32bits systems hit the limit more easily and that makes the error apparent.

Migrating to 64bits does not fix it, just makes it take longer (probably much longer) to happen.