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

when use trace_processor_shell load long trace file , process is killed and echos "Killedg trace: 1248.58 MB" #1046

Closed
gaozig opened this issue Mar 18, 2025 · 5 comments

Comments

@gaozig
Copy link

gaozig commented Mar 18, 2025

perfetto_trace_shell version
Perfetto v49.0-33a4fd078 (33a4fd0)
Trace Processor RPC API version: 14

@stevegolton
Copy link
Member

It looks like the first part of 'Loading trace: XXX' message has been overwritten with 'Killed', which happens when the process is terminated. I'd suspect an OOM?

It looks like your trace at least 1248MB, which is on the large side, I'd expect you'll require a fair bit of available memory to be able to load it into trace processor.

@stevegolton
Copy link
Member

I'll close this issue as it doesn't seem to be a problem with trace processor.

@gaozig
Copy link
Author

gaozig commented Mar 19, 2025

the following version works pretty welll, no killed occur
Perfetto v39.0-d9ce4c0af (d9ce4c0)
Trace Processor RPC API version: 10

@gaozig
Copy link
Author

gaozig commented Mar 19, 2025

@stevegolton

@stevegolton
Copy link
Member

I wouldn't be surprised if more modern versions of TP use more memory. We typically optimize for speed, not memory footprint. It's also possible there could be a bug that just happens to be triggered by your trace, but I can't help you much given the information you've shared. If you want us to help you'll need to help us reproduce the bug by sending us:

  • The offending trace.
  • Your system specs.
  • Kernel logs which could indicate whether an OOM has occurred and why.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants