Author Topic: Malloc Errors YAY  (Read 1061 times)

0 Members and 1 Guest are viewing this topic.

This happens when I try to start a mission. This only seems to happen when I load WiH2. WiH1 -seems- to work fine.


Code: [Select]
Malloc Failed!

KERNELBASE.dll! IsNLSDefinedString + 1221 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_7_2_RC5_SSE.exe! <no symbol>
fs2_open_3_7_2_RC5_SSE.exe! <no symbol>
fs2_open_3_7_2_RC5_SSE.exe! <no symbol>
fs2_open_3_7_2_RC5_SSE.exe! <no symbol>

[attachment kidnapped by pirates]

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
A "Malloc Failed!" error sounds like you're running out of memory. Try deleting/moving these files:
Code: [Select]
F:\games\Freespace 2\blueplanet2\adv-bp2.vp
F:\games\Freespace 2\blueplanet\adv-bp.vp
F:\games\Freespace 2\mediavps_2014\MV_Advanced.vp
The "Advanced" VPs contain massive textures that take up a lot of memory, and you may not even be able to notice the quality difference at your resolution of 1366x768.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.