Skip to content
Discussion options

You must be logged in to vote

One report for all processes: no. memray flamegraph reads one capture file, so it is one report per child. Give each child its own -o, because the default report name drops the PID and every child gets the same name.

The .bin.PID names are by design: a child writes to the parent's file name plus its PID.

Empty files with --aggregate and --follow-fork: not your setup. The aggregated file is written only when tracking ends, and pool workers exit through os._exit, which skips that. I reproduced it with memray 1.20.0. For pool workers keep the default format.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@godlygeek
Comment options

@sanzoghenzo
Comment options

Answer selected by godlygeek
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants