[Adderbane]

Finally got through to Universal Truth in the new WiH, and this happens while loading just after completing the Idun Dictionary retrieval mission...  I've seen similar problems before, and last time I fixed it by removing the advanced textures.  I've already removed the BP advanced ones and the advanced from the 2014 MVPs.  Any ideas?

Build: 3.7.3 (0ea25e7) SSE2

[attachment DELETED!! by Strong Bad]

[TrickMagnet]

having the same error as well, updated the files from the launcher too to get all the latest patches and bugfixes currently available. can't upload my log atm since i literally just happened to notice this thread on my way out the door to work, will do when i get back

[Dragon]

There is a build in the SCP forum with "Large Address Aware" functionality. Try this. You're simply running out of memory, UT is quite a hog in that regard.

[General Battuta]

But I don't understand why it is. Out of curiosity, could you run the installer one more time and see if it updates your visual VPs? We recently compressed some textures better to reduce size.

[niffiwan]

Actually, try the 64bit builds not the "Large Address Aware" ones.

Regarding the cause, I wonder if there's a relation to the amount of time played, i.e. it'll only occur after a few missions. If so that could point to a memory leak somewhere, or perhaps just memory fragmentation.

[Adderbane]

Tried rerunning the installer, no change.  I'll try the 64 bit build tomorrow when I get a chance.  The crash only occurs at UT, and the first time it happened I'd played Finest Hour and the mission before UT (name I can't remember) without problems.  So it doesn't really seem to be something that occurs after playing for an extended time.

[AdmiralRalwood]

The crash only occurs at UT, and the first time it happened I'd played Finest Hour and the mission before UT (name I can't remember) without problems.  So it doesn't really seem to be something that occurs after playing for an extended time.

...In the same session? Because that actually would be running for "an extended time".

[TrickMagnet]

good news is that the 64 bit sse2 fixed my game (mostly?) to play ut2. that ending was amaaaaaaaazing by the by

as for the original client i patched (?) moments before i made my post, so unless it was updated very very recently i believe i should have everything to its most recent editions. i'm down to help track down bugs and post logs to help snuff it out though, just tell me where to shoot

[Cobra]

Actually, try the 64bit builds not the "Large Address Aware" ones.

Regarding the cause, I wonder if there's a relation to the amount of time played, i.e. it'll only occur after a few missions. If so that could point to a memory leak somewhere, or perhaps just memory fragmentation.

It has to be a memory leak of some sort... I experienced the issue every couple of missions in the latter half of WiH2. I have a hard time believing 12GB isn't enough.

[Phantom Hoover]

It has to be a memory leak of some sort... I experienced the issue every couple of missions in the latter half of WiH2. I have a hard time believing 12GB isn't enough.

If you're running FSO on Windows and using any build that isn't the 64-bit one that niffiwan linked then you don't have 12GB of memory, you have 2.

[Cobra]

It has to be a memory leak of some sort... I experienced the issue every couple of missions in the latter half of WiH2. I have a hard time believing 12GB isn't enough.

If you're running FSO on Windows and using any build that isn't the 64-bit one that niffiwan linked then you don't have 12GB of memory, you have 2.

*facepalm* This is what I get for late night/early morning posting.

[m!m]

The memory likely increases over a few missions because loaded models aren't unloaded when the mission ends because they could be used in another mission. Or it could be a memory leak in which case it needs to be fixed.

[crizza]

tried the 64bit build, but still the malloc, but hey, I'm used to it^^

[AdmiralRalwood]

tried the 64bit build, but still the malloc, but hey, I'm used to it^^

...Are you sure you were running the 64-bit build? How much RAM does your system have?

[crizza]

My bad, the launcher stopped working with the 64bit build and only launched the game with the latest nightly.
As of today, 12gb RAM.

[m!m]

Yeah, a 32 bit launcher with a 64 bit binary will probably lead to issues. You could try launching the .exe directly from the explorer.

[AdmiralRalwood]

Oh right, I forgot to include "don't try to run it through the launcher" to the 64-bit build post. Let me add that now.

[crizza]

Uh, right. How do I tell the exe which mod I want to play, without the launcher? I'm not good at this...

[tomimaki]

Edit cmdline_fso.cfg in fs2_root_folder\data

[AdmiralRalwood]

Uh, right. How do I tell the exe which mod I want to play, without the launcher? I'm not good at this...

Edit cmdline_fso.cfg in fs2_root_folder\data

And/or just use the launcher, but point it to a 32-bit build (and then quit it immediately); the cmdline_fso.cfg file it generates will be read by the 64-bit build just fine.