@Spectator That has nothing to do with your physical memory. I think that crash was caused by a leak of some sort, cause a trigger or action that is bugged and is impossible to execute, but the game still tries to execute it and fails = crash. :/ It probably does not have anything to do with your PC specs, but if it did mean memory then it would be referring to the working aka, RAM and not to HD memory. I think even an infinite amount of RAM could not stop a crash like that.
But good on you to report it since it says exactly what line of code caused it to crash.

Informative x 1

My blood cries out for the vengeance of my people's blood, which can only be repaid with at least twice as much blood or maybe 3 times as much blood,LIKE IF YOU WENT TO HELL AND IT WAS FULL OF BLOOD AND THAT BLOOD WAS ON FIRE AND IT WAS RAINING BLOOD, THEN MAYBE THAT WOULD BE ENOUGH BLOOD! ...ehmm but probably not.
- anonymous Blood Mage.

​

... But we are still the Nathreziim! We will not let some upstart human get the best of us. A high elf mayyybe, but a human = NEVER!​

It's the second time in row I got this error as Scourge. I have never gotten crashes before, only quite rarely and i always used to be last to crash. Now I crashes first, two times in a row on Blue. When I used to crash before on LTA or any map It would never usually give me an error. This time it is giving me error details and I only had this issue in current patch.
Only explanation i have for this is my C: Drive now has only 80G left where it used to have more memeroy left before but I don't think it is related to this.@SvnmS can you confirm please If the error is either caused by me or Scourge or LTA in general?

Click to expand...

Some trigger is leaking, Probably the legion pathing triggers, @Yousef can de-activate them for the next version and see how that goes. I have no idea why they leak though, they shouldn't unless some units are being removed without being killed, which rarely happens in LTA.

Some trigger is leaking, Probably the legion pathing triggers, @Yousef can de-activate them for the next version and see how that goes. I have no idea why they leak though, they shouldn't unless some units are being removed without being killed, which rarely happens in LTA.

@Spectator That has nothing to do with your physical memory. I think that crash was caused by a leak of some sort, cause a trigger or action that is bugged and is impossible to execute, but the game still tries to execute it and fails = crash. :/ It probably does not have anything to do with your PC specs, but if it did mean memory then it would be referring to the working aka, RAM and not to HD memory. I think even an infinite amount of RAM could not stop a crash like that.
But good on you to report it since it says exactly what line of code caused it to crash.

Click to expand...

Thanks for the help, I can see what happened now.

I just wasn't sure why was it me who had to crash both games being on blue. I checked the games on stream, nobody else seemed to crash afterwards. I did not even touch outland portals . I have a 16GB Ram, I highly doubt other people I was playing with could have higher RAM.

So my best guess is the crashes is purely random then? It's not related to RAM or Faction or what you are doing before the crash? It just crashes cause of a trigger leak and the game decides to drop one player on random? I guess it was just bad luck it was me twice in a row on scourge, got LK in both.

As far as i know, memory leaks are not due to your RAM max size. But the memory w3 uses from ur laptop. It is programed to use X amount of it, to do its processes, and if the game exceeds it, it crash. Ofc we are talking about memory leaks due to too much triggers or stuff working at the same time, or a bug, that makes w3 engine cry and collapse. Not talking about people playing in wooden pcs that explodes when a simple fight occurs. But with your 16GB RAM we can discard the "wooden pc" option .

As far as i know, memory leaks are not due to your RAM max size. But the memory w3 uses from ur laptop. It is programed to use X amount of it, to do its processes, and if the game exceeds it, it crash.

Click to expand...

Hmm I wonder if there is way to increase the X amount Warcraft is programmed to use? It's probably too technical for us.

Ofc we are talking about memory leaks due to too much triggers or stuff working at the same time, or a bug, that makes w3 engine cry and collapse. Not talking about people playing in wooden pcs that explodes when a simple fight occurs. But with your 16GB RAM we can discard the "wooden pc" option .

Click to expand...

Yea the crashes I had were not in big fights or anything, it was actually moments were it was pretty quiet and i was not doing anything.

One Thing I still don't understand is why is it a certain someone crashes? Shouldn't everyone crash at the same time if the Leaks are too much or IF a trigger is looping or if a trigger is referenced to a non-existent data? I have seen it where everyone crashes at the same time and that makes sense.

However It makes no sense to me why I for example dropped in that game and others where fine, even the leak was caused by Legion portal triggers??? Shouldn't everyone drop? This is why I still think Makemehost or the connections have something do with this since It doesn't make logical sense, specially since I probably was the one in game with highest RAM.

If you actually look at the error MMH gave when I Crash it is: Elucinator (host's name) : "iliya has lost the connection (connection error - ECONNRESET)

See it talks about connection, IT was not a Desync error. Tho not my internet connection was fine since I was on Twitch and it did not interrupt or anything so It was not my interest's fault either. It surprising even tried to reconnect me for 1 second before dropping:

@SvnmS I just realized, apparently the last trigger to go off exactly before I crashed was IronForge being destroyed. Not sure if that has anything to do with it. If you want I might be able to get replay from Zoom and check exactly every event before the crash, do you reckon that will be useful?

@SvnmS Sorry to bother you again and Sorry for Double post, Can't edit on phone atm. I was just wondering are you sure crashes have nothing to do with GetLocalPlayer() functions? I know disconnects related to player specific events are technically meant to come up as Desyncs Not a disconnect but Just want to be double check. Maybe not all the triggers that are player specific with GetLocalPlayer were made compatible with 1.49?

It's just I don't think The Legion portal triggers you added are really the reason and don't want you to have to remove them without proof since those triggers are awesome.

@SvnmS Sorry to bother you again and Sorry for Double post, Can't edit on phone atm. I was just wondering are you sure crashes have nothing to do with GetLocalPlayer() functions? I know disconnects related to player specific events are technically meant to come up as Desyncs Not a disconnect but Just want to be double check. Maybe not all the triggers that are player specific with GetLocalPlayer were made compatible with 1.49?

It's just I don't think The Legion portal triggers you added are really the reason and don't want you to have to remove them without proof since those triggers are awesome.

Click to expand...

I'm not sure, I think it always comes as a desync, unless the actions inside a "GetLocalPlayer() = Player(x)" condition causes a crash by itself.
But the possibility that it is legion pathing triggers is still high, so de-activating them to see if they were the reason and re-activating the if they aren't should help

The time counter and CP counter used to be combined into the same thing, now they're kinda next to each other and colliding a bit. I know it's a minor thing and that it happened because of the 1.29 Blizz patch. But still if you could just make them the way they were before it'd be perfect.

My blood cries out for the vengeance of my people's blood, which can only be repaid with at least twice as much blood or maybe 3 times as much blood,LIKE IF YOU WENT TO HELL AND IT WAS FULL OF BLOOD AND THAT BLOOD WAS ON FIRE AND IT WAS RAINING BLOOD, THEN MAYBE THAT WOULD BE ENOUGH BLOOD! ...ehmm but probably not.
- anonymous Blood Mage.

​

... But we are still the Nathreziim! We will not let some upstart human get the best of us. A high elf mayyybe, but a human = NEVER!​