safe_malloc failed on allocation of 8256 bytes

For now: Everything about NetRadiant

Moderator: Moderators

safe_malloc failed on allocation of 8256 bytes

Postby Grasshopper » Sat Sep 26, 2009 12:41 am

safe_malloc failed on allocation of 8256 bytes

that is the error i have gotten on 2 maps ive tried doing anywhere from(test) to full compile .

the number of bytes in the error string are different for the maps . Google has brought up a couple of things but none seems relevant to netradiant . they say use a -lomem switch , but im not sure how . others have said things about configuring the shader file ??!! . Im on brand new pc and cant understand why my previous slow computer with less memory could handle mikee sized map compiles and this one cant .

I've made sure all ram hogging programs are closed . I've tried to compile with previous version of nexuiz . and messed with page file cache . same problem
Master ? Do you call me Grasshopper because I am cunning and stealthy?
NO ! Because you are Ugree , Rike insect !
Grasshopper
Alien
 
Posts: 228
Joined: Sat Feb 02, 2008 9:44 am
Location: Dead Guy In Nexuiz

Postby mand1nga » Sat Sep 26, 2009 1:42 am

Netradiant or Nexuiz? If you're talking about the former please post this error on http://dev.alientrap.org/projects/show/netradiant

Cheers
mand1nga
Alien trapper
 
Posts: 321
Joined: Mon May 12, 2008 12:19 am

Postby divVerent » Sat Sep 26, 2009 9:27 am

I'd need your map files plus all used shader and textures to debug that.
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again

You can vary the number of "MS", so you can clearly see it's MS which is causing it.
divVerent
Site admin and keyboard killer
 
Posts: 3809
Joined: Thu Mar 02, 2006 4:46 pm
Location: BRLOGENSHFEGLE

Postby Grasshopper » Sat Sep 26, 2009 10:10 am

http://grasshopper.nexuizninjaz.com/hells_gate_b4.pk3

here is beta version 4 , compiled under fourth option from the top . thanks for your time
Master ? Do you call me Grasshopper because I am cunning and stealthy?
NO ! Because you are Ugree , Rike insect !
Grasshopper
Alien
 
Posts: 228
Joined: Sat Feb 02, 2008 9:44 am
Location: Dead Guy In Nexuiz

Postby Grasshopper » Sat Oct 10, 2009 9:59 pm

bump

i seem to have found a way around it . like radiant said disable build process monitoring . so i did and i can compile fully now and the process log is in /.netradiant /1.5.0/junk.txt

in linux it gave me the error " could not find suitable socket on #### "

after watching system monitor it shows that the ram usage goes all the way to 2Gb and the swap file pegs out also . Now build monitoring off shows the same thing but it keeps going . beware pc may run really slow during this time . be patient
Master ? Do you call me Grasshopper because I am cunning and stealthy?
NO ! Because you are Ugree , Rike insect !
Grasshopper
Alien
 
Posts: 228
Joined: Sat Feb 02, 2008 9:44 am
Location: Dead Guy In Nexuiz


Return to NetRadiant - General Discussion

Who is online

Users browsing this forum: No registered users and 1 guest