***Erlang/OTP 22*** [erts-10.4] [source] [64-bit] [smp:6:6] [ds:6:6:10] [async-threads:1] [hipe]
Eshell V10.4 (abort with ^G)
1> q().
ok
2> [root@kyu-renu-stdportal1 ~]# cat /etc/centos-release
***CentOS Linux release 7.6.1810 (Core)***``
hudson2010
0
darnahsan
0
hauleth
darnahsan
thats why I shared as crash was erlang related not elixir
seeing other weird crashes as well, maybe the dependencies are not ready for 1.10.0 hence the crashes
0
josevalim
Creator of Elixir
Oh, good find. Please open up a issue on the honeybadger library. Elixir v1.10.0 adds more logging metadata, which is a good thing, but those libraries are assuming that everything in the metadata can be converted to JSON - which was never true. 
3
hauleth
It is the same problem as in this topic
All is about the fact that Jason.encode is not enough to encode logger metadata as specs define it as keyword() which mean that not all values will have defined protocol. 1.10 adds few default metadata, that are types not supported by default in Jason (PIDs and tuples). So it need to be fixed in LoggerJson, as this used wrong assumptions about data types in metadata.
2
sorentwo
Oban Core Team
Issue was reported and is already fixed. The Honeybadger library attempts to recursively escape into an encodable format, in this case it wasn’t handling functions.
https://github.com/honeybadger-io/honeybadger-elixir/pull/259
1