Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken flame graph #3939

Open
kolesnikovae opened this issue Feb 21, 2025 · 0 comments
Open

Broken flame graph #3939

kolesnikovae opened this issue Feb 21, 2025 · 0 comments
Assignees
Labels
type/bug Something isn't working

Comments

@kolesnikovae
Copy link
Collaborator

Flame graph structure might be broken in certain cases:

Image

I was able to reproduce the issue only with Go heap alloc_* profile types (heap inuse_* are fine). My understanding is that it might be caused by the fact that these are cumulative profiles.

On the other hand, the exported pprof is valid and does not appear to be malformed. Importing it via ad-hoc profiles results in a valid flame graph. My theory is that the data gets corrupted either during its journey from the data blocks to the query frontend, or while converting the tree to a flame graph.

Might be related:

@kolesnikovae kolesnikovae added the type/bug Something isn't working label Feb 21, 2025
@kolesnikovae kolesnikovae self-assigned this Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant