From my own experience with debugging memory issues, you can quickly check if it is related to monster culling by going back to the commit before
PR#156 was merged, and seeing if the crash still happens. If it doesn't, you can probably walk through each individual commint in 156 to get a better idea of the cause (not squashing PRs suddenly coming in handy).
Also based on my experience the fact that CFiredCharacterCommand is in the stack trace probably means it is an issue with character culling.
____________________________
[Insert witty comment here]
Qzvlkx?