Hard Light Productions Forums

Hosted Projects - FS2 Required => Blue Planet => Topic started by: Crybertrance on January 11, 2013, 09:23:48 am

Title: Another Malloc Failed? [FIXED]
Post by: Crybertrance on January 11, 2013, 09:23:48 am
So, I'm getting another Malloc Failed. This after completing the Jupiter Orbit mission (Idune Dictionary?) and proceeding to the next mission. The loading slider goes all the way to the right, and then, this:

Code: [Select]
Malloc Failed!

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

I don't think this is a pilot issue, because I can do everything else (access mainhall, replay other missions from the techroom, etc) without issue.

log: http://pastebin.com/fxidVBye (http://pastebin.com/fxidVBye)
Title: Re: Another Malloc Failed?
Post by: General Battuta on January 11, 2013, 09:35:59 am
If you quit and try to load the mission again, do you still get the error?
Title: Re: Another Malloc Failed?
Post by: Crybertrance on January 11, 2013, 09:39:05 am
If you quit and try to load the mission again, do you still get the error?

Yes...consistently. However sometimes I get a shorter Malloc Failed error like so:

Code: [Select]
Malloc Failed!

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
Title: Re: Another Malloc Failed?
Post by: SF-Junky on January 11, 2013, 11:23:23 am
It worked fine for me after I had deleted that uber big file.

Of course I had to re-play the missions I had already done to this point.
Title: Re: Another Malloc Failed?
Post by: Crybertrance on January 11, 2013, 11:27:11 am
It worked fine for me after I had deleted that uber big file.

Of course I had to re-play the missions I had already done to this point.

Are you talking about the player files? If so, the debug log shows parsing of the pilot files worked just fine?
 :confused:
Plus I don't wanna replay everything again! I just scraped through "Her Finest Hour" by the skin of my teeth!
Title: Re: Another Malloc Failed?
Post by: niffiwan on January 11, 2013, 06:28:08 pm
Your log shows that your not crashing during the loading of the pilotfile, so this must be a different malloc error to the other one.  I'm not sure what is causing this one :(
Title: Re: Another Malloc Failed?
Post by: Crybertrance on January 12, 2013, 03:50:33 am
Your log shows that your not crashing during the loading of the pilotfile, so this must be a different malloc error to the other one.  I'm not sure what is causing this one :(

So, then, what should I do? Anything I can try out here?

e: Maybe I could load another pilot and use that hot-key (what was it again?) to unlock all the missions and then play from the techroom to see if I can repro the Malloc?
Title: Re: Another Malloc Failed?
Post by: General Battuta on January 12, 2013, 10:46:18 am
That would be great.
Title: Re: Another Malloc Failed? [FIXED]
Post by: Crybertrance on January 13, 2013, 04:03:37 am
That would be great.

Nope that did not help, but I found the cause of the problem (thanks to The_E and MatthTheGeek) over at #bp.

Apparently; Blue Planet is designed and tested to be compatible with only it self and the MediaVps as stated by The_E. So, as pointed out by Matth, this custom flag was causing issues:

Code: [Select]
-mod updated_ships
This is where I had stored all the HTL stuff released since the MediaVPs released.

And since in Universal Truth the only non-HTL ship is the
Spoiler:
Sathanas
FSO was choking on the HTL Awesomeness of said ship ( since after all, there are so many of them!)

So, I removed that flag and guess what, no errors! I ran the whole mission at a solid 30 FPS (And you thought the HD 5700 series is a poor card  :hopping: )

So thanks guys! :)
Title: Re: Another Malloc Failed? [FIXED]
Post by: crizza on January 16, 2013, 04:29:31 pm
Is this the same issue?
Code: [Select]
Malloc Failed!

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
Title: Re: Another Malloc Failed? [FIXED]
Post by: niffiwan on January 17, 2013, 04:50:08 am
It is hard to tell just from that error.

Check the size of your pilot files - if they are huge, then it's the "other" malloc issue.  Also post a fs2_open.log and we might be able to give more info.