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

client and server process name entries in android_binder_txns seem to be cut off #1012

Closed
13100D opened this issue Feb 12, 2025 · 1 comment

Comments

@13100D
Copy link

13100D commented Feb 12, 2025

hello,
when i attempt to use the android_binder_txns table, some entries for the process names appear to be cropped off. i am attaching some screenshots for the same along with trace files and apk files for the applications for recreation.
i use the following sql command and am able to observe entries that seem to be incomplete

INCLUDE PERFETTO MODULE android.binder; SELECT client_process,server_process FROM android_binder_txns;

following are the android version, sdk version and the model name for my device

hanoip:/ $ getprop ro.build.version.release 12 hanoip:/ $ getprop ro.build.version.sdk 31 hanoip:/ $ getprop ro.product.model moto g(40) fusion

Image
here Packageinstaller seems to be cutoff and shows up as ackageinstaller.

Image
this is another scenario where motorola.camera.3 and android.apps.photos seem to be cropped off

Github does not allow me to upload the trace files so i will share a drive with the respective traces and apks

https://drive.google.com/drive/folders/132LeRdRgCXjzW5D9cop1DrbM102zjaLu?usp=sharing

@aMayzner
Copy link
Collaborator

aMayzner commented Feb 13, 2025

The 15 character limitation is a Linux limitation which applies for all data source coming from Linux kernel ftrace. However, Perfetto also supports scraping /proc to obtain the full process names from /proc//status. This can be enabled by added the following to the config:

data_sources: {
    config {
        name: "linux.process_stats"
        process_stats_config {
            scan_all_processes_on_start: true
        }
    }
}

Unless the process is very short lived (i.e. we don't have enough time to actually manage to scrape /proc before the process dies), process names should always be present with that config.

When you want to verify if the issue was caused by some postprocessing in SQL or is this a problem with process names, I recommend also taking a look into process table, which is included by default.

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