You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PID 55 starts, allocates a chunk, logs a duration begin event.
PID 55 then forks a child of PID 66
They both log a duration end event
Currently, this means that sort of bad things will happen. The SHM chunk will probably be shared between processes (I'm not entirely sure), and on top of that, screwy things happen to the events.
I'm not sure what the right fix for this is, as we can't easily know which "side" of the fork is actually supposed to win. I think we may need a way to flag a chunk as being "ghost events", which are copied from the parent's, and used in the child if necessary (e.g. if an end is seen with no matching begin, try find a ghost event that matches it, otherwise the ghosts are just ignored).
An alternative might be to just say "sorry, don't expect events to work across fork boundaries", and drop them, but that seems a bit harsh.
The text was updated successfully, but these errors were encountered:
Picture:
Currently, this means that sort of bad things will happen. The SHM chunk will probably be shared between processes (I'm not entirely sure), and on top of that, screwy things happen to the events.
I'm not sure what the right fix for this is, as we can't easily know which "side" of the fork is actually supposed to win. I think we may need a way to flag a chunk as being "ghost events", which are copied from the parent's, and used in the child if necessary (e.g. if an end is seen with no matching begin, try find a ghost event that matches it, otherwise the ghosts are just ignored).
An alternative might be to just say "sorry, don't expect events to work across fork boundaries", and drop them, but that seems a bit harsh.
The text was updated successfully, but these errors were encountered: