Results 1 to 9 of 9

Thread: safe_malloc Error - how q3map2 handles 1GB more RAM

  1. #1

    safe_malloc Error - how q3map2 handles 1GB more RAM

    This is a workaround for the safe_malloc Error in the Light stage in a Windows 7 64bit environment, if you get something like this:

    --- SetupTraceNodes ---
    ************ ERROR ************
    safe_malloc failed on allocation of 957874176 bytes
    It doesn't solve problems if you have too complex maps but it could expand the amount of memory q3map2 can use by 1GB avoiding the use of the lomem switch. I simply "patched" the q3map2.exe header with the "App can handle > 2GB address space" flag. Without that, q3map2 always crashed wenn the memory consumption reached 2GB. Now it crashes at about 3GB. A 64bit q3map2 release would be much better, but this workaround here could work for some people, too.

    I tested it with the latest q3map2.exe from Netradiant, you should make a backup of it before you start if it doesn't work:

    1. Download the CFF Explorer Suite
    2. Open CFF Explorer and then open your q3map2.exe file.
    3. Go to the "File Header" section (under Nt Headers)
    4. click the "Click here" on the Characteristics row on the right hand
    5. check the "App can handle >2gb addressest" box, then click OK
    6. go to "Save as", and then rename your existing q3map2.exe (for backup)
    7. Save the current version as q3map2.exe

    Kind regards, Christian
    Atta Way, Baby!

  2. #2

    Re: safe_malloc Error - how q3map2 handles 1GB more RAM

    Nice!

    But why "App can handle >2gb addressest" is unchecked by default?
    http://www.youtube.com/user/DonnovanBRA Donnovan Youtube Channel.
    http://code.google.com/p/glory-of-the-weak Map Glory of the Weak on Google Code.
    https://twitter.com/DonnovanBR Donnovan Twitter

  3. #3

    Re: safe_malloc Error - how q3map2 handles 1GB more RAM

    Don is making ET maps now?

    ETQW Mediocre Club

  4. #4

    Re: safe_malloc Error - how q3map2 handles 1GB more RAM

    Thanks this thread is money

  5. #5

    Re: safe_malloc Error - how q3map2 handles 1GB more RAM

    Suggested solution confirmed here too.
    YouTube | Twitch | Homepage | Twitter | Facebook

    Operating System: Windows 10 Home 64-bit
    . Processor: Intel i7-2600 CPU @ 3.4 GHz (8 CPUs). Memory and graphics: 12Gb RAM, NVIDIA GeForce GTX 970. Resolution and sound: 1920 x 1080 (16:9), Realtek Audio.

  6. #6

    Re: safe_malloc Error - how q3map2 handles 1GB more RAM

    obsidian do we still need this with the new settings?

  7. #7

    Re: safe_malloc Error - how q3map2 handles 1GB more RAM

    Another probable cause:
    http://forums.warchest.com/showthrea...l=1#post454393

    As for the workaround, when the 1.6.4 will be released, I don't think it will be needed

    Quote Originally Posted by Krischan
    A 64bit q3map2 release would be much better, but this workaround here could work for some people, too.

  8. #8

    Re: safe_malloc Error - how q3map2 handles 1GB more RAM

    Indeed not, the upcoming version GtkRadiant 1.6.4 will have both 32-bit and 64-bit compilers for Windows (Linux and Mac users already have 64-bit versions). So if you're on a 64-bit system, no need for -lomem or this funny hack. Just choose the right compiler you want to use and everything is a piece of cake.

  9. #9

    Re: safe_malloc Error - how q3map2 handles 1GB more RAM

    Could you explain why you registered to resurrect this topic with basic mapping knowledge?

    GtkRadiant 1.6.4 includes a x64 compiler now btw.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •