Re: [Chrome DevTools] CPU Profiler not working

[Yury Semikhatsky]

Can share the page that you are profiling?

Yury

On Tue, Apr 2, 2013 at 9:26 AM, Abe Burnett <abe.b...@gmail.com> wrote:

I'm new to Developer Tools (just working through the excellent Code School coverage of it) and I'm in section 6.2 which covers the CPU profiler. The issue I'm having is that I click on the Profile tab, then ensure that Collect Javascript CPU Profile is selected and press the "Start" button. After interacting with the page, I click to stop it and then select the created profile below CPU PROFILES. However, when I do, I don't see anything other than 100.00% idle and 0% program. I assume it's operator error--since I'm new to Developer Tools--but I can't imagine what I might be doing wrong. 

I'm using Chrome 27.0.1453.9 dev-m. Thanks in advance for any assistance you can provide.

Warm regards,

Abe

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Yury Semikhatsky]

I've just checked with Chrome 27.0.1453.3 on Mac and it worked fine for me. Can you open attached page, open Profiles panel and then click "Start profiling" button in the page. In the collected profile top-down view you should see most of the time spent in the onclick handler, can you confirm that?

Yury

[bob....@sansio.com]

I am having the same issue.  When I use Yury's cpu.html page it seems to work (I can see an onClick call).  But when I, for example, try to profile this google groups page and collapse/expand various portions of the screen, I just get the idle 100% and program 0%.  I'm using Sencha Touch for most of my development and this is very js heavy but I cannot get it to show anything else.  

Thanks

Bob

[bob....@sansio.com]

Oh and here's the capture for Yury's page. 

On Tuesday, April 2, 2013 12:26:32 AM UTC-5, Abe Burnett wrote:

I'm new to Developer Tools (just working through the excellent Code School coverage of it) and I'm in section 6.2 which covers the CPU profiler. The issue I'm having is that I click on the Profile tab, then ensure that Collect Javascript CPU Profile is selected and press the "Start" button. After interacting with the page, I click to stop it and then select the created profile below CPU PROFILES. However, when I do, I don't see anything other than 100.00% idle and 0% program. I assume it's operator error--since I'm new to Developer Tools--but I can't imagine what I might be doing wrong. 

I'm using Chrome 27.0.1453.9 dev-m. Thanks in advance for any assistance you can provide.

Warm regards,

Abe

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you have received this transmission in error, please delete it from your system without copying it, and notify the sender by reply email so that our address record can be corrected

[bob....@sansio.com]

And from this google groups page. 

[bob....@sansio.com]

Last Thing (probably unless I figure out what's wrong). 

I'm using windows 7 with Chrome Version 27.0.1453.47 beta-m

Thanks

Bob

[Ilya Tikhonovsky]

Hi guys.

I managed to reproduce the bug on Windows platform.

The affected versions are 27.0.1453.47 beta-m and corresponding dev channel version.

I've created a bug https://code.google.com/p/chromium/issues/detail?id=232347

Please star it if you'd like to track the status.

The profiler works fine on other platforms.

Also it works fine on the current DevChannel m28 or stable version of Chrome.

Regards,
Tim.

--

[oden...@gmail.com]

I also have this problem.  27.0.1453.56 beta 

Canary doesn't: 28.0.1483.0 canary

This agent based model: http://goo.gl/8vC4G

Shows:

While it should show:

[Ilya Tikhonovsky]

The path has been reverted so the next beta 27.0.1453.61 will work fine. 

Regards,
Tim.

--

[Owen Densmore]

Whew, thanks Tim!  Hard to know when something's a bug or not, nice having canary to check with.

[Ilya Tikhonovsky]

s/path/patch/

Regards,
Tim.