I wasn't able to reproduce the issue but we had multiple reports of the same issue. Here's a screenshot of one reporter that indicates that it is somehow still possible to click outside of the image bounds which will lead to a crash.
Maybe we should try to disable the bounds checking for clicks during debugging and make it robust enough to work/not crash in that situation, before enabling the bounds checking again.