tp: Track process lifecycle from Android framework events#5214
Open
tp: Track process lifecycle from Android framework events#5214
Conversation
In some traces, ftrace only captures an initial process snapshot. Subsequent starts and deaths come from the Android framework via AndroidProcessStartEvent (process_bound) and AndroidBinderDiedEvent (binder_died) track events carrying pid, uid, and process_name. Hook into ProtoToArgsParser::AddParsingOverrideForType to intercept these events during arg parsing. For starts, reuse the existing process if ftrace already created it (filling in uid only), otherwise create one via StartNewProcessWithoutMainThread. For deaths, set uid/name on the process row before marking it ended. Add ProcessTracker::EndProcess() to handle ending processes created both with and without a main thread. Add ProcessTracker::UpidForPid() as a public lookup (previously test-only). Change-Id: I167ed69400f3bbc5f9f753407cdbfae83110fd3f
🎨 Perfetto UI Builds
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In some traces, ftrace only captures an initial process snapshot. Subsequent starts and deaths come from the Android framework via AndroidProcessStartEvent (process_bound) and AndroidBinderDiedEvent (binder_died) track events carrying pid, uid, and process_name.
Hook into ProtoToArgsParser::AddParsingOverrideForType to intercept these events during arg parsing. For starts, reuse the existing process if ftrace already created it (filling in uid only), otherwise create one via StartNewProcessWithoutMainThread. For deaths, set uid/name on the process row before marking it ended.
Add ProcessTracker::EndProcess() to handle ending processes created both with and without a main thread. Add ProcessTracker::UpidForPid() as a public lookup (previously test-only).