New issue
Advanced search Search tips

Issue 601760 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2016
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Feature



Sign in to add a comment

Provide DTrace probes for Chrome

Reported by kenorb@gmail.com, Apr 8 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36

Steps to reproduce the problem:
My Chrome is constantly slow, and I'd like to know what it's exactly doing in real-time.

I've checked on OS X by:

  sudo dtrace -l | grep -i chrom

and I don't see any static probes.

So the aim of this issue is to investigate whether it's possible to implement static probes for certain actions such as request being made, extension is being invoked, something is rendered, etc.

What is the expected behavior?
I was expecting some probes, so I can debug the requests and performance for specific actions, similar as for PHP or MySQL (e.g. http://php.net/manual/en/features.dtrace.dtrace.php, https://dev.mysql.com/tech-resources/articles/getting_started_dtrace_saha.html).

What went wrong?
Chrome is freezing my OS X all the time by making mouse pointer to spin. Tested on different profiles with different extensions. Probably because of too many tabs (which I need on daily basis).

Did this work before? N/A 

Chrome version: 49.0.2623.87  Channel: n/a
OS Version: OS X 10.11.2
Flash Version: Shockwave Flash 21.0 r0
 

Comment 1 by kenorb@gmail.com, Apr 8 2016

Currently I could only do only: sudo fs_usage | grep -v 0.00

15:44:30  select  0.011450   Google Chrom
15:44:30  select  0.010346   Google Chrom
15:44:30  read    0.023206   Google Chrom
15:44:30  select  0.012441   Google Chrom
15:44:30  select  0.012458   Google Chrom
15:44:30  select  0.011435   Google Chrom
15:44:30  select  0.011439   Google Chrom
15:44:30  read    0.023190   Google Chrom
15:44:30  select  0.011778   Google Chrom
15:44:30  select  0.011769   Google Chrom
15:44:30  select  0.011402   Google Chrom
15:44:30  select  0.011397   Google Chrom

which is meaningless and killing the most consuming group of tabs is just one-time off problem. So DTrace probes would allow the people to debug the Chrome in meaningful way.
Labels: Needs-Feedback
Status: WontFix (was: Unconfirmed)
Thanks for your report.

Do chrome://tracing or chrome://profiler provide any of the information you need?

I don't think we are likely to implement dtrace probes for Chromium, since we mostly lean on our own tracing and profiling infrastructure.

Comment 3 by kenorb@gmail.com, Oct 11 2017

Btw. chrome://profiler has been removed as per  Issue 739505 

Sign in to add a comment