Received unexpected trace event (:gc_minor_start & :gc_minor_end) about flame_on HOT 6 CLOSED

This has been resolved in the underlying library that we rely on, but a new version of that hasn't been cut since it was merged. I will push a new version of Flame On once they cut a new version.

from flame_on.

This has been resolved in the underlying library that we rely on, but a new version of that hasn't been cut since it was merged. I will push a new version of Flame On once they cut a new version.

Hi I also have the same error. May I know if you have any advise on a workaround in the meantime like the necessary code changes if that is restricted to only the library? Many thanks.

[info] Received unexpected trace event: {:trace_ts, #PID<0.1614.0>, :return_to, {:mnesia_tm, :execute_outer, 6}, {1647, 523491, 570412}}
[info] Received unexpected trace event: {:trace_ts, #PID<0.1614.0>, :return_to, {:mnesia_locker, :rlock, 3}, {1647, 523491, 570447}}
[info] Received unexpected trace event: {:trace_ts, #PID<0.1614.0>, :return_to, {:mnesia_tm, :reverse, 1}, {1647, 523491, 570545}}
[info] Received unexpected trace event: {:trace_ts, #PID<0.1614.0>, :unlink, #PID<0.934.0>, {1647, 523491, 570589}}
Output filename: flame_on_output_delete_me/1647523491011574-eflambe-output.bggg

I have incorporated your commit into eflambe into my local copy already - but the above error still occurs - the flamegraph fails to generate in the LiveDashboard. And even that, in my LiveDashboard, the log does not appear.

from flame_on.

@gaslit are you having issues beyond the warnings in the logs? Is the flamegraph rendering? If not, is that output file present in your project? This ticket is in regards to :gc_minor_start and :gc_minor_end warnings which are red herrings and can be ignored. The :return_to messages I have also seen during normal runs. The :unlink one is new to me.

from flame_on.

I have edited my post.

1. No other issues

2. Flamegraph does not render. Even the logged messages does not appear on the LiveDashboard. But yes, they appear on the console as usual.

3. Output file does not exist: Output filename: flame_on_output_delete_me/1647524175532330-eflambe-output.bggg but i thought it is deleted after creation

Many thanks

from flame_on.

I can confirm this, I get many "Received unexpected trace event" both in my M1 dev and in Heroku. Also, the flamegraph doesn't render in many occasions.

from flame_on.

Thank you everyone for your reports on the issue of flamegraphs not rendering. This ticket is being used to track the :gc_* warnings in the logs, and #9 is tracking the issue of flamegraphs not rendering (they are unrelated), so if you are having issues with flamegraphs not rendering, subscribe to #9 for updates (and check out #11 which should either resolve these issues directly or give us the tools to be able to diagnose them)

from flame_on.