<div dir="ltr"><div><div>Hi folks,<br><br></div><div>In sasl logs I'm observing some stack-traces that I can't explain, on Erlang 18.1 + actively using HiPE compilation. Looks like those are stack-traces of 2 different processes somehow merged together.<br><br></div><div>Here are some examples:<br></div><div><br>** {function_clause,[{gb_trees,delete_1,2,[]},<br>                     {gb_trees,delete,2,[]},<br>                     {mirrored_supervisor,init,1,[]},<br>                     {gen_server2,handle_msg,2,[]},<br>                     {mirrored_supervisor,init,1,[]}]}<br></div><div><br>mirrored_supervisor:init/1 is<br><a href="https://github.com/rabbitmq/rabbitmq-common/blob/stable/src/mirrored_supervisor.erl#L276">https://github.com/rabbitmq/rabbitmq-common/blob/stable/src/mirrored_supervisor.erl#L276</a><br></div><div>But there is no way it can call:<br></div><div>- itself recursively<br></div><div>-  gen_server2:handle_msg/2<br></div><div>- gb_trees:delete/1<br></div><div><br></div><div><br></div><div>** {function_clause,[{rabbit_channel,handle_info,2,[]},<br>                     {gen_server2,handle_msg,2,[]},<br>                     {ssl_config,module_info,1,[]}]}<br></div><div><br>And according to this trace, `ssl_config:module_info/1` somehow started process of message handling in generic server, which doesn't make any sense. And this `module_info` happens with a lot of different modules, both built-in and application specific.<br></div><div><br><br></div><div>Is this something known? Can it be related to HiPE? I was not able to find anything related to stacktraces in release notes of every 18 and 19 release.<br></div><div><br><br></div>Best,<br></div>Alexey<br></div>