• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!
  • ✅ The POLL for Hive's Texturing Contest #34 is OPEN! Vote for the TOP 3 SKINS! 🔗Click here to cast your vote!
  • ✅ The POLL for Hive's Techtree Contest #20 is OPEN! Vote for the TOP 3 FACTIONS! 🔗Click here to cast your vote!

[JASS] memory exhausted

Status
Not open for further replies.
Level 10
Joined
Apr 3, 2006
Messages
535
Okay, so i know what this means, but how can i go about fixing this. Ive learnt it basicly says i have to many triggers, or variables and i need to reduce because wc3 is at its limit??

apart from triggers, what can i trim down on to get this to go away!
 

Attachments

  • memory exhausted.JPG
    memory exhausted.JPG
    116.5 KB · Views: 275
memory exhausted doesn't mean what you think it means. It means that the memory of the syntax checker (and not of the game) has been used up. What this most probably means is that you have a syntax error somewhere that's leading the syntax checker in a huge loop until it uses up all the memory available.

You're using Jass New Gen pack so the normal world editor debugger is replaced by pjass which is a third party addition not affiliated to blizzard at all actually.

Try going back and undoing what you most recently did. The error is probably there. What did you add before it stopped passing the syntax check?
 
hmmmm, weird i have been managing now for a while by deleting un used triggers that i used to keep for reference and it goes away. If i add 1 extra trigger though this comes up everytime untill i delete 1 trigger. I'm not sure what made this error come up, but is it possible to disable the jass checker and ignore the problem? :D
 
Actually yes you could disable the jass checker, but I'm surprised you're having this error at all. How many triggers do you have exactly? To disable Jasshelper -> Uncheck "Enable Jasshelper" Though if you make any mistakes in your code it won't tell you and the map simply wont run.

Maybe you should think of lightening the trigger amount? What exactly are you doing that uses so many triggers?
 
its an RPG map i have been working on for like 3 - 4 years, and there are quite a few triggers :D
 
Status
Not open for further replies.
Back
Top