Editor bug; map rescue needed?

[Eaglendia]

Hey, y'all - been a minute.
The map I've been working on seems to have encountered a corruption or issue of some variety when saving: not sure how, given my editor didn't even crash.

The map loads fine in WC3 with all assets and data intact, but can't be launched in the Editor—it crashes at a specific point during loading triggers, and I've heard this might be due to an unfixed bug with GUI trigger comments (I primarily use GUI)
I'm hoping that there's an MPQ wizard that might know how to approach solving the problem, as I'm looking at losing an astronomical amount of work if it turns out to not be recoverable. Thanks in advance for any help!

Update: Issue didn't reproduce on a different computer. Currently attempting a scan-and-repair to see if that solves anything.

Double Update: In light of this, a full reinstall seems to have solved the issue. Go figure—I'll try to be more careful in the future.

 

[emperor_d3st]

Always keep backups.

 

[Uncle]

I recently had an issue where I could no longer open a map and it seemed to be related to an HD model that I imported. The solution was to have someone else open the map and save it as a new file. I was then able to open this new save file, delete the model, and proceed from there.

I only started experiencing this bug somewhat recently (maybe 1.34+?).