not sure about the `catch` here. It seems to change the semantics from the original implementation, irrespective of dropping messages due to `noconnect`, `nosuspend`. For example, pre-this change `unregistered_local_processs ! something` would crash the vnode, here it will fail silently. The former may not necessarily be the better behaviour but do we want to make that sort of change in this PR? Seems like we can remove the `catch` and still get what we want (from the documentation I dont see `erlang:send/3` throwing errors any differently than `!`)