I'm getting this exact same error stack, but it's triggered by instance_destroy. Using 1.0.38 with GMS 2.3.1.53
Can you run the game in debug mode and see what the value of e.message is (or what e generally is)? I cannot seem to reproduce this locally
e.message
e
Edit: also pushed a new update (1.0.39) with more error handling in this regard.
