[erlang-questions] etop flooded with "Erlang top got garbage" messages

[Mike Cugini]

Hey all,

I was recently put on an erlang project, and I've been trying to get etop 
working to help profile some issues our app has been having (mostly 
interested in Message Queue sizes).

Etop is started with this command:

erl -name etop@<ip> -hidden -s etop -s erlang halt \
               -output text -sort reductions -lines 50 \
               -node <node_name> -setcookie <cookie>

Whenever I start etop, I see a flood of "Erlang top got garbage" messages:

Erlang top got garbage {trace_ts,<5261.332.0>,out,
                                 {gconnection,process_sock_loop,2},
                                 {1363,141107,842108}}
Erlang top got garbage {trace_ts,<5261.378.0>,out,
                                 {gconnection,process_sock_loop,2},
                                 {1363,141107,842471}}
Erlang top got garbage {trace_ts,<5261.351.0>,out,
                                 {gconnection,process_sock_loop,2},
                                 {1363,141107,842670}}
Erlang top got garbage {trace_ts,<5261.424.0>,out,
                                 {gconnection,process_sock_loop,2},
                                 {1363,141107,842861}}

This sometimes results in the connection dropping after this message: 
Output server crashed: connection_lost

>From what I've gathered, etop can be disrupted in this way by tracing, and 
as far as I can tell, our codebase does not use tracing anywhere (no 
references to erlang:trace or dbg).

Initially we thought it might be related to using the lager logging 
library, but even after disabling it, the issue has persisted.

Are there any other potential causes of this issue?  Or perhaps something I 
am overlooking?

Thanks!
Mike Cugini
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130312/eb2f06d0/attachment.htm>