Bug 74076 (AUDIT) - Web Inspector: "Network Utilization" audit can not finish
Summary: Web Inspector: "Network Utilization" audit can not finish
Status: RESOLVED FIXED
Alias: AUDIT
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows 7
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-08 04:46 PST by Oleg
Modified: 2012-01-26 01:50 PST (History)
10 users (show)

See Also:


Attachments
The state of inspector (51.82 KB, image/jpeg)
2011-12-08 04:46 PST, Oleg
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oleg 2011-12-08 04:46:24 PST
Created attachment 118362 [details]
The state of inspector

good day,
I tried to use WebInspector Audit on our web product.
As for "Web Page Performance" - all OK, I click "Run" and get result.
But "Network Utilization" can not finish and output results. I click "Run", and progress began, button "Run" became disabled. But result absent in 1 hour, and even 1 day later.
I am very upset. Please tell me, how to debug web inspector, I'll try to find the cause of such behaviour. Is it any possibility to write log for audit? Or force audit to stop? 
On any other site audit is workink OK, but with our software - not. I want to find a bug in our software, may be something force audit to continious recursion?
Comment 1 Oleg 2011-12-08 04:48:26 PST
I tried Safari 5.1.2 and Chrome 15.0.874
Comment 2 Alexander Pavlov (apavlov) 2011-12-08 04:59:30 PST
The canary Chromium (tip of tree) has the capability of stopping the running audit, and you can debug Chrome DevTools using the procedures described at http://www.chromium.org/devtools.

On a similar note, it would be extremely useful if you could come up with a publicly available test URL that reproduces the problem.
Comment 3 Oleg 2011-12-08 05:10:40 PST
I'll try to provide public URL
Comment 4 Oleg 2011-12-08 06:51:02 PST
try cp(dot)crucialserver(dot)com
Comment 5 Pavel Feldman 2011-12-08 06:56:35 PST
@alexander: I might have fixed it while compiling the front-end: http://trac.webkit.org/changeset/96949
Downstream issue: http://code.google.com/p/chromium/issues/detail?id=98846.
Comment 6 Oleg 2011-12-08 07:05:01 PST
how can I update my WebInspector in Chrome? Is it possible? Please give me link link with description if it exists
Comment 7 Pavel Feldman 2011-12-08 14:49:12 PST
(In reply to comment #6)
> how can I update my WebInspector in Chrome? Is it possible? Please give me link link with description if it exists

It'll update automatically to v16 soon. However, you can use one of the early access channels to get new development features earler:
http://www.chromium.org/getting-involved/dev-channel
Comment 8 Alexander Pavlov (apavlov) 2012-01-26 01:50:23 PST
(In reply to comment #5)
> @alexander: I might have fixed it while compiling the front-end: http://trac.webkit.org/changeset/96949
> Downstream issue: http://code.google.com/p/chromium/issues/detail?id=98846.

Seems fixed in Chrome 17.