André Pinto

I have attached the perfcollect.log file of the latest collection I did yesterday. [perfcollect.log](https://github.com/microsoft/perfview/files/9505300/perfcollect.log)

``` # lttng create Spawning a session daemon Session auto-20220908-131306 created. Traces will be written in /root/lttng-traces/auto-20220908-131306 # lttng add-context --userspace --type vpid Error: vpid: UST create channel failed Warning:...

I tried running a different container on the same host with the same configuration except for the docker image (I used the base image of the container with the problem)...

I'm seeing a similar pattern when running a rancher cluster (the container gets restarted): ``` Mar 12 11:27:20 ip-10-51-46-0 dockerd[1202]: time="2018-03-12T11:27:20.722227268Z" level=error msg="attach: stderr: write unix /var/run/docker.sock->@: write: broken pipe"...

It's not very common, I agree. But it may happen (it actually did in our project). I think conceptually "not found" and "empty" should be treated differently, but it is...

yes, that's what I meant. email_address should be a field. it does change the email in that case.