malloc failure

[Namdrol]

And another problem!

Trying to beta test Fidcal's latest mission and it won't load.

I get to the mission is loaded, please wait stage and it freezes for about 3 minutes and then dumps me out giving this message, (or variations but always the same malloc failure #)(with a whole load of other warnings which Fidcal says aren't important)

 

Shutting down sound hardware

idRenderSystem::Shutdown()

Shutting down OpenGL subsystem

...wglMakeCurrent( NULL, NULL ): success

...deleting GL context: success

...releasing DC: success

...destroying window

...shutting down QGL

...unloading OpenGL DLL

------------ Game Shutdown -----------

--------- Game Map Shutdown ----------

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

Shutdown event system

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

malloc failure for 4194312

 

 

I'm running the latest version of TDM and Doom is fully patched, all the other missions will load and run fine.

My specs are -

Pentium DualCore T4400 @ 2.2ghz

Onboard Intel 4 series using 1 gig

3 gig Ram

Win7

 

I've nothing running in the background and tried reinstalled my graphics drivers.

[stumpy]

malloc errors have something to do with running out of memory.

Have you tried increasing your virtual memory, thats where windows uses harddrive space as memory I've got mine set to 3 gigabytes. Although dont know how to set it in win7.

Edited March 30, 2010 by stumpy

[Fidcal]

I'd have thought 3GB of RAM more than enough. It's worth saying that all the other beta testers are running it OK so it's puzzling. I'm running it on two machines one of which has only 2GB and an old FX5900 with about 256MB I think or less.

 

I'm going to try a special version with a little ripped out but why does it work on other machines?

 

Is there any texture config that would help?

 

How about a physical RAM test. Probably find some free software on the net just in case there is a glitch in the RAM?

[Namdrol]

Got my vm set to 4.5g so unlikely to be that.

Will try a physical memory test.

[Fidcal]

Namdrol: I've uploaded a slightly reduced version to try @

 

http://shalebridgecradle.co.uk/testing/viewtopic.php?p=17608#p17608

[jdude]

Also try closing as much background stuff as possible.

[Goldchocobo]

It's the onboard video... not a ram issue.

I went from 2 gigs to 6 - TDM utilizing an available 4gb on the latter (since its a 32bit app), with 0 difference in the variance in malloc errors. In other words, I tested the "limits" of a TDM map, down to a couple of rooms/patches, and the 2 systems made no difference.

[Fidcal]

But I'm running it on an old FX5900 with only 128MB of memory on a PC with only 2GB of RAM which is why it is so puzzling.

[stumpy]

all i can find about 'malloc failure for 4194312' is an openGL error and the solution is to update drivers. And thats off the blackcat forums.

Edited April 1, 2010 by stumpy

[Goldchocobo]

But I'm running it on an old FX5900 with only 128MB of memory on a PC with only 2GB of RAM which is why it is so puzzling.

 

That's still a lot better then virtually anything onboard - it's at this point, not a matter of ram, but graphics cards. Nvidia has always been better then intel int he graphics department as well (obviously).

[Fidcal]

Ah right. Interesting. I didn't realize onboard graphics would be so far behind. But I guess if one bought a standard PC there is no need and a PC sold as a 'games' machine would have something better anyway.

 

Well, if that is the cause then I don't feel quite so bad that I've done something wrong with my FM like some bad overcomplicated terrain.

 

So Namdrol need only buy a cheap second hand half reasonable old graphics card for $25 and it might solve this?

[New Horizon]

So Namdrol need only buy a cheap second hand half reasonable old graphics card for $25 and it might solve this?

 

Or potentially, it may just be as simple as a driver update...according to Stumpy's post.

[Namdrol]

Hey guys thanks for the responses.

I'm on a laptop so a new card isn't an option!.

I'm running the most recent drivers. (First thing I checked.)

What does puzzle me though is that I can run every other mission except this.

Including both for TDM1.01, Stumpy's and Railgun/Springheels.

 

Oh well, I'm buying a new rig in 6 months or so.

Edited April 1, 2010 by Namdrol

[Serpentine]

You can try dropping the texture detail, AF/AA. Its most likely just that the mission uses a lot more in the way of different material shaders and your driver is having trouble allocating resources above some arb point, its unlikely to fix it but here's hoping