search

travistang / speedtracer

Automatically exported from code.google.com/p/speedtracer
0 stars 0 forks source link

Aborted XHRs duration is gigantic (never stops) #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Provide a description of the buggy behavior observed:

What steps will reproduce the problem?
1. Vist http://jsbin.com/isolo with speedtracer
2. Click to view network resources
3. Notice that the duration of the xhr that was aborted (/isolo) never 
finishes (and therefore seems very large).

Give a description of the behavior you expected to see.
I expected that the the length of an aborted XHR to be something smallish 
(around 2 seconds), but it something quite large like 30-60 seconds 
(depends on the current size of your timeline "window")

The version of Speed Tracer (check the chrome://extensions url)
Version 0.8

The build of Chrome you are using (check the About Chrome dialog)
5.0.307.11 beta for mac

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

Original issue reported on code.google.com by timm...@gmail.com on 4 Mar 2010 at 6:54

GoogleCodeExporter commented 9 years ago 
Thanks for the bug report. It appears that this has been fixed (or I am unable 
to 
reproduce it) in the latest version: 0.14. Your unusual use of the 'HTML' XHR 
method 
did uncover a small bug in the validation schemas, and I'll be putting up a 
patch for 
that shortly.

Original comment by con...@google.com on 21 May 2010 at 11:10