Event capture seems to fail for certain pages

[GoogleCodeExporter]

Provide a description of the buggy behavior observed:

Pages (or whole sites) load correctly in Chrome, but when started in
SpeedTracer, no events seem to be captured.

The behaviour is quite consistent during a period of a few hours: pages
that did not show events in ST, later worked fine, and again a day later
did not.

There seems to be a threshold, that somehow can be influenced by the
refresh button. By clicking the refresh button and inmediately clicking the
stopwatch, those pages with problems do sometimes successfully show in ST.
It requires really immediate consecutive action, you cannot wait too long
after clicking the refresh button.

Some network problem might be a cause, because two of the sites that do not
load at all might very well reside on the same physical machine or at least
in the same network. Both sites include js includes from google maps or
google analytics, so I thought that might interfere too. But even a simple
html fails to load, so that seems not to be the problem (unless some
caching mechanism keeps blocking the site after the initial failure)

What steps will reproduce the problem?
1. Use my computer in my network (until now I seem to be the only one to
experience this behaviour, I am in a home ADSL network, which is at times a
bit slow)
2. Load page in Chrome (e.g. http://www.stumbleupon.com/)
3. Click stopwatch
4. No events are captured, the default config-error message will show (**)
5. Now refresh (key shortcut) and immediately click the stopwatch button again
6. Most of the times the page will now correctly show events in ST  

Give a description of the behavior you expected to see.

A list of events, without having to use the refresh button. (Most sites
show correctly without the need of just-before-refresh). Two sites
consistently do not show events (http://virtualconcepts.nl/ and
http://codediggers.nl/).

I reproduced it on windows xp and mac os x 10.6.2

The version of Speed Tracer (check the chrome://extensions url)
0.6 (Windows XP and Mac OS X)

The build of Chrome you are using (check the About Chrome dialog)
Windows XP: 4.0.266.0
Mac OS X: 4.0.272.0 (34671)

Please also provide any exceptions or screenshots that would be pertinent.
See http://code.google.com/p/speedtracer/wiki/HowToReportAnIssue

Speed Tracer monitor window:
 - only worker-script imported messages, no javascript errors
exceptions in the Speed Tracer extension:
 - no information at all in the console of the speed tracer extension
Note: after activating the speed tracer extension console, going back to
the speed tracer now shows one paint event, but that I guess that is just
the re-activation of the speedtracer screen that does that (screenshot
attached)

** 
default config-error message means:

"No data received in 6 seconds. Chrome must be run with the flag: 
'--enable-extension-timeline-api'.
See getting started for more details."

Original issue reported on code.google.com by codedigg...@gmail.com on 19 Dec 2009 at 5:06

Attachments:

• oneeventafterconsole.tiff

[GoogleCodeExporter]

I build the extension and it was automatically installed in Chromium on the Mac 
as
version 0.7. And again something changed for the better: http://codediggers.nl 
does
now load for me, although with very low probability even with the "refresh-first
workaround". 

This race condition seems also to influence the event list, see attached 
screenshots
"cd-7events.tiff" and "cd-11events.tiff" (in zip). I *think* speedtracer should 
give
the same events for a page every time. I might very well be naive here...

The other page that I never was able to show in SpeedTracer
(http://virtualconcepts.nl) is still not shown, whatever I do. And I could also 
not
get it working by going to the speed tracer extension console. For a moment I 
thought
that that action sparked the 'good behaviour' of showing http://codediggers.nl 
in ST.

Another thing I now saw, in the console with which I start Chromium on my Mac
(--enable-extension-timeline-api arg), I see this error repeating:

chrome-extension://ognampngfcbddbfemdapefohjiobgbdl/hintletengine/rules/hintlet_
mozilla_hash.js:1866:
Uncaught TypeError: Cannot read property 'length' of undefined

No further exceptions in either console

Original comment by codedigg...@gmail.com on 19 Dec 2009 at 7:58

Attachments:

• cd-eventlists.zip

[GoogleCodeExporter]

The last site (http://virtualconcepts.nl) now also loads with the workaround 
(refresh
and immediately click stopwatch button), but never without the workaround. 

Thanks for looking into it, if I can do some extra testing with a new revision, 
just
let me know.

Original comment by codedigg...@gmail.com on 20 Dec 2009 at 5:38

[GoogleCodeExporter]

Hi,

I have an hypothesis: I think the speedtracer starts listening to page load 
events
too late. If I give Chrome something to do by prior to the load, less (or even 
none)
load events/resources are missed.

This behaviour only applies to loading the page. If all page load related 
events are
missed, mouseovers over active elements on a page work correctly (my bad: after 
load
*all* sites work well, even though the error message is displayed)

Original comment by codedigg...@gmail.com on 21 Dec 2009 at 9:45

[GoogleCodeExporter]

Here is what I hypothesize is causing your trouble:  once Speed tracer gets its 
first 
event, the timeline starts animating.  By default, the first four seconds are 
shown 
in the current window.  To see anything beyond the first four seconds, you must 
adjust the overview window using the zoom or by manipulating the grips in the 
overview graph to change the current window.

When you encounter this problem, I'm wondering if hitting the 'Zoom All' button 
might 
quickly confirm whether this is right.  Zoom all the button just to the left of 
the 
page transition drop down (the one with URLs in it).

Another thing you could try is to open a new tab to create a 'blank' tab, press 
the 
speed tracer icon, and then put in the url http://virtualconcepts.nl/  This 
will give 
you a clean page transition and the first 4 seconds will be the website loading 
http://virtualconcepts.nl, not your mouse moving over the previously loaded web 
page.

Original comment by zundel@google.com on 22 Dec 2009 at 2:58

[GoogleCodeExporter]

Original comment by knor...@google.com on 21 Jun 2011 at 7:11

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I am closing this issue. Please repost if there are related concerns.

Original comment by sarahgsm...@google.com on 4 Aug 2011 at 12:49

• Changed state: Done