I cannot preview the triggers of the current version, but there are several issues with the older version, they might lead to crashing. Not sure about desync tho.
If these are not fixed in the current version, please take a look.
1) You are not storing global weather effects into any variable. All the triggers run with "destroy last created weather effect", although the weather effects are created trough multiple triggers.
And since they use entire map, they sure eat alot of memory from the map.
2) Timers should always be also destroyed, like timer windows. If you only destroy the timer window == the timer will continue counting till the end of times.
3) Untitled trigger 011 leaks multiple locations every time it is ran. (8 in total) Running every 65 seconds. If the the conditions are met every 65 seconds, after playing for around 3 minutes you have 24 locations leaking. Eating up memory.
On a side note: You can reduce the number of triggers by a great amount by using playerinteger. For example: You currently have 2 triggers for EVERY player hero revive.
Since you use timers here too, and they are also never destroyed, after some time, im pretty convinced this will cause issues.
This map would benefit greatly from a DDS (Damage detection system). You have triggers with "a unit is attacked", which should rarely or never be used at all. Since it can lead to exploits and unwanted results.
You could try disabling this Easy Item Stack 'n Split v2.7.4 - GUI in your map and the see if it still crashes, desyncs or whatever. This is the only trigger I found this far that uses GetLocalPlayer function.
