Pete Stevenson

Hi @c3-pranjaysagar , The best case scenario for debugging this is if you could supply a mostly self-contained way to reproduce the bug. If you have an application that you...

Hi @c3-pranjaysagar , Could you provide some more details on your setup and how to reproduce the issue? Here are some things that might be helpful for us to debug:...

The env. var. `PL_PROFILER_JAVA_SYMBOLS` needs to be set to `true`. There is a related question though: why is your env. var. set to false. We are looking at the version...

Hi @c3-pranjaysagar , Good to know that you found a work around. I am currently investigating the theory that there is some override for the default value of the Java...

We saw #594 also. Thank you for filing the separate issue. For the profiler, there are some knobs we can tune to see if the stack traces you observe better...

@scomri I just faced the same issue. It turns out that I had some `amqp` traffic on my cluster, which, thanks to a bug, causes the `pem` (Pixie edge module)...

Hi @asasas234 , Is it possible that you are looking at a NodeJS application? We do not support symbolization for NodeJS yet. Although we plan to add NodeJS symbolization, we...

Hi @asasas234 , The flamegraph image you provide looks good to me. The "address" at the root of the stack `0xe0000ae38` is probably not a valid instruction pointer address. The...

Hi @asasas234, Could you take a look at the script `px/stirling_errors`? There will be a row populated for each process that does not have frame pointers enabled. My best guess...

Hi @RomanAgeev , If possible, can you send us the the logs (`px collect-logs` or `kubectl -n pl logs vizier-pem-abcde`) or write up a method by which we can reproduce...