paulirish / speedtracer Goto Github PK

When Speed Tracer is ran on an application not connected via network (e.g. 
local files), Speed Tracer doesn't collect any data.

What steps will reproduce the problem?
1. Open local app w/o server side scripting in Chrome
2. Start Speed Tracer
3. Play with app
4. Wait 6 seconds for Speed Tracer to fail to collect any data.

Speed Tracer should collect data regardless of the file location. Without 
collecting local data, there is no way to truly identify bottlenecks in JS 
code. This is particularly crucial when developing apps that are designed 
to work offline.

Speed Tracer Version: 0.14

Chrome Version 6.0.401.1 dev

Provide a description of the buggy behavior observed:

What steps will reproduce the problem?
1. Go to http://desktop.google.com/ or any url with download links
2. Click on the Speed Tracer icon.
3. Now in the desktop.google.com, Click on Install Google Desktop
4. It starts downloads, but it leads to page error in the browser and also the 
speed tracer doesnt capture the response details.

Give a description of the behavior you expected to see.
Page error should not occur and response details(time,..) has to be captured.

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

The build of Chrome you are using (check the About Chrome dialog)
6.0.453.1

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

What feature are you requesting?

Provide the Extension module as a standalone GWT library.

What benefits would the feature provide?

Allow others to easily begin building Chrome extensions using GWT. Allow for 
others to contribute improvements to the Extension module.

Briefly describe any workarounds available:

Extract the code from the com.google.gwt.chrome.crx package and bundle it 
into a seperate jar for personal use.

---
I've begun hacking on this this a bit, adding simple message passing, and 
working on support for options pages.

I'm trying out Insight and Speed Tracer. I'm not able to see any Insight 
information on Speed Tracer (I've done the same as on the video available at 
http://www.springsource.org/insight).

Insight it self works: I'm able to drill down until the SQL statements.
Speed Tracer seams to work either even if 
- I don't see Request and Response headers (see also issue 28, 
http://code.google.com/p/speedtracer/issues/detail?id=28&q=header)
- nor Insight information.

I'm using the latest versions of every tools:
SpringSource Tool Suite 2.5.1
Chrome 9.0.572.1
Speed Tracer (by Google) - Version: 0.18

And I'm working on Mac OS X 10.6.5.

Thanks in advance for any hint on this regard.

PS: See also same post on spring forum, 
http://forum.springsource.org/showthread.php?p=330441#post330441

What steps will reproduce the problem?
1. switched to Dev Channel
2. Added "C:\Users\shiva\AppData\Local\Google\Chrome\Application\chrome.exe 
--enable-extension-timeline-api"
3. downloaded the extension n error thrown - Extension Install Error. 
Invalid value for 'permissions[0]'

What is the expected output? What do you see instead?
Install error instead of successfull installation

What version of the product are you using? On what operating system?
Google Chrome is up to date (3.0.195.33)- Windows Vista Home Premium

Please provide any additional information below.

I've just committed the headless extension into the SVN repo along with some
tests, but we need to document the API and some ways to use it.

After carefully following all directions, I receive "No data received in 6 
seconds..." error.

Followed the http://code.google.com/webtoolkit/speedtracer/get-started.html 
instructions exactly. Tried it on both Windows 7 and current Ubuntu installed 
on a MacBook Pro. Same results.

Give a description of the behavior you expected to see.

Google Chrome   11.0.686.3 (Official Build 76659) dev
WebKit  534.23 (trunk@79757)
V8  3.1.6.1
User Agent  Mozilla/5.0 (Windows; Windows NT 6.1) AppleWebKit/534.23 (KHTML, 
like Gecko) Chrome/11.0.686.3 Safari/534.23
Command 
Line    "C:\Users\peter\AppData\Local\Google\Chrome\Application\chrome.exe" 
--flag-switches-begin --flag-switches-end

SppedTracer 0.20

See:
http://friendfeed.com/mmastrac/fd24d39a/today-mystery-what-
happening-in-these-two-html

What feature are you requesting?

Ability to load a URL from the SpeedTracer window.

What benefits would the feature provide?

Currently, you can load a page, press the SpeedTracer button and trace the 
page. Making the url Drop Down a DropDownCombo (editable) with some "Start" 
button capability would allow a developer to profile arbitrary requests.

Briefly describe any workarounds available:

None that I know of.

Even when files are being loaded from cache, they have a "From Cache" value 
of "false" and show an HTTP status of "200".

Chrome version: 6.0.408.1 dev

To reproduce: navigate to a page where resource files are known to be in 
browser cache.  Files will show a load time of 0 or 1 ms but will still have 
"From Cache" value of false.

thanks,

-Nick  

A SpeedTracer user that has caching configured correctly for the .nocache.js 
file sees  hintlets pop up in SpeedTracer:

http://groups.google.com/group/speedtracer/browse_thread/thread/ea740ce88465
339

The attached speedtrace (I edited it with a  text editor, so it probably 
won't load in a browser) shows that the caching is turned off in several 
different ways.

At r69, some backTrace resource URLs are being returned as 'undefined' from 
chromium's timeline records.  This was noticed when browsing maps.google.com 
(see attachment)

Provide a description of the buggy behavior observed:

What steps will reproduce the problem?
1. Open chrome with --enable-extension-timeline-api flag
2. Navigate to http://google.com/
3. Click Speed Tracer icon

After 6 seconds the following appears:

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

Give a description of the behavior you expected to see.
Speed Tracer page opens and starts working

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

The build of Chrome you are using (check the About Chrome dialog)
16.0.912.21 dev-m

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

See also http://code.google.com/p/chromium/issues/detail?id=77123

Speed Tracer Trampoline File displays 
"Loading Speed Tracer for: http://localhost:8888/Test2.html"
forever.

What steps will reproduce the problem?
1. Install into Eclipse
http://google-web-toolkit.googlecode.com/svn/2.1.0.M2/eclipse/plugin/3.6
2. Create a new Web Application Starter Project
3. Run "Profile As | Speed Tracer" from project context menu
   Console tab displays: Compiling module com.example.myproject2.Test2 ...
   Chrome with "Speed Tracer Trampoline File" is opened
4. Double-click on URL "http://localhost:8888/Test2.html" on Development Mode 
tab
   Second Chrome tab with "Speed Tracer Trampoline File" is opened
5. Copy and paste "http://localhost:8888/Test2.html" into 3rd Chrome tab
   Web Application Starter Project page is displayed 

Speed Tracer should appear in the 1st and 2nd Chrome tabs.

The version of Speed Tracer (check the chrome://extensions url): 0.17
The build of Chrome you are using (check the About Chrome dialog): 6.0.472.0 dev
Windows 7 Pro

Regards,
Miloslav Skacel

In the Breaky test, we are seeing periodic failures that are caused by
a timeout.  What we believe is happening is that there is a race
condition between the time it takes headless_content_script.js to issue a 
chrome.extension.connect() and HeadlessBackgroundPage.java actually creating 
the port.  If the background page is slow to come up, it will never receive 
the onConnect event and further messages from the content script will fail.

A workaround is to start up the browser, wait, then navigate to a new page 
before staring the test.   A more permanent fix would be to put a timeout 
and re-connect in the content script and logic in the background page to 
acknowledge the onConnect event back to the content script.

The 2 divs approach currently in the headless extension patch could interfere
with some applications.  

Example: go to google.com. Type in the search "cnn" and click on the first 
link. Sometimes the "new" URL is not cnn.com but a resource load.

Looking at the events coming through, there is a Profiler.resetProfiles after 
the initial load, but nothing to clearly indicate that the main resource is a 
page transition. Appears to be an issue with Chrome and extensions. 

current r364

Run speed tracer from any URL and then manually type a new URL in the address 
bar. The manually typed URL does not appear in the history drop down (although 
pages from clicked links do).

Take an app that definitely runs an onunload handler and transition to 
another page. In Speed Tracer, select the previous page from the select box 
and notice that no onunload event is shown.

Notices in r301:

When launched from a New Tab (blank page), the Speed Tracer window is not
controlled properly from the Speed Tracer browser action.  I noticed these two 
problems:

1) The speed tracer browser icon does not change to the monitoring state (red 
squiggle instead of green squiggle in the stop watch)

2) If you close speed tracer window, it does not pop back up when you hit the 
browser action again.

Provide a description of the buggy behavior observed:

Whenever I press the "Discard Data and Reset" button, Speed Tracer will no 
longer log any events from the webpage.

What steps will reproduce the problem?
1. Go to http://www.google.com/
2. Open Speed Tracer. Observe Speed Tracer capturing events.
3. Hit the "Discard Data and Reset" button.
4. Observe that no events are now being captured.

Give a description of the behavior you expected to see.
Events still being captured after the "Discard Data and Reset" button is 
pressed.

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

The build of Chrome you are using (check the About Chrome dialog)
5.0.375.38 beta

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

Provide a description of the buggy behavior observed:

What steps will reproduce the problem?
1. Reload any page
2. Go to view Network
3. Look at the network resource bars

Give a description of the behavior you expected to see.

Start and end.

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

0.24

The build of Chrome you are using (check the About Chrome dialog)

16.0.899.0 (Official Build 103668) dev

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

The hintlet indicators in the attached screenshot did not actually occur on 
the chrome://newtab page - they occurred after I loaded an app and a page 
transition occured.

SpeedTracer gets page transition notices after the actual page transition 
begins.  The next page adjusts its start time backwards to find the true 
page transition (start of the main resource load).

What seems to be happening here is that the previous page length is not 
adjusted accordingly.

Validating using DumpValidator.validate(record) a record of type 12 
(RESOURCE_SEND_REQUEST in SpeedtracerSchemas.java). Including the field 
"duration" fails validation, even though it is listed as an "optional" field in 
the schema. 

record without "duration" validates:
{"data":{"identifier":6,"url":"http://www.google.com/","requestMethod":"GET"},"t
ype":12,"usedHeapSize":1792352,"totalHeapSize":3928256,"time":4243.961181640625}

added duration, won't validate:
{"data":{"identifier":6,"url":"http://www.google.com/","requestMethod":"GET"},"d
uration":120,"type":12,"usedHeapSize":1792352,"totalHeapSize":3928256,"time":424
3.961181640625}

Error message: "The property "duration" is not defined in the schema and the 
schema does not allow additional properties"

The schema definition for this type in SpeedtracerSchemas.java

"NETWORK_RESOURCE_START" : {
       "description" : "A network request is enqueued",
       "id" : "NETWORK_RESOURCE_START",
       "type" : "object",
       "extends" : {"$ref" : "TIMELINE_EVENT_MARK"},
       "properties" : {
         "type" : {"type" : "integer", "minimum" : 12, "maximum" : 12},
         "duration" : {"type" : "integer", "optional" : true},
         "data" : {
           "type" : "object",
           "properties" : {
             "identifier" : {"type" : "integer", "description" : "Integer id of this resource" },
             "url" : {"type" : "string", "description" : "URL Requested"},
             "requestMethod" : {
               "type" : "string",
               "description" : "Method used to retrieve the resource. (e.g. GET/POST)"
             }
           },
           "additionalProperties" : false
         },
         "additionalProperties" : false
       }
     }

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."

What feature are you requesting?

V8 has a number of different garbage collection types (scavenge, 
non-compacting, full compacting), each with different performance 
characteristics.  Is it possible for Speed Tracer to distinguish between these 
types of collections?

What benefits would the feature provide?

When building large javascript applications, it would be nice to have a closer 
look into when the garbage collector is running which type of collection.  
There could be significant gains to be had if you could find and optimize the 
spots in your code where you're putting a lot of stress on the memory 
management system.

I have no idea if you're instrumenting into V8, or if V8 exposes this kind of 
information to Chrome when it garbage collects, but if the information is 
available, it'd be nice to see this distinguished on those events.

In Firebug, the Resources/Console tabs show the request and response data for 
XHRs (it even parses the response if it is JSON and shows it via an expandable 
tree). Because all my XHRs are to the same URL (with variable POST data), I 
cannot tell which ones are slow and which ones are fast from Speed Tracer.

Provide a description of the buggy behavior observed:

What steps will reproduce the problem?
1. Open Chrome DevTools,
2. Open speedtracer
3. You will see: 
Pfffttt, Speed Tracer is not working.

Please double check a couple of things:
You must start Chrome with the flag: --enable-extension-timeline-api
You must be running the Chrome Dev channel.
For more details, see our getting started docs.


Give a description of the behavior you expected to see.

Working normally.

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

0.24

The build of Chrome you are using (check the About Chrome dialog)

Google Chrome   16.0.899.0 (Official Build 103668) dev
OS  Linux
WebKit  535.6 (@96469)
JavaScript  V8 3.6.4.1


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

Speed Tracer reports that Chrome is sending out multiple requests (10+) at the 
same time.  Looking at the packets with Wireshark, Chrome is never sending out 
more than 6 concurrent requests.

Even looking at Speed Tracer (see attached screenshot), it is clear that the 
first six responses come back nearly in unison.  The network graph makes it 
seem as though Chrome sent the other requests at the same time and that the 
application cannot handle those additional demands.

What steps will reproduce the problem?
1. Access a web page with CSS and JS in the <head> and 10+ images in the 
<body>.  I was running against a node.js application on port 3000.
2. Look in the Network tab of Speed Tracer (see attached).

Based on what Wireshark is saying, I expect that the first 6 images will be 
requested and responded to *before* a single request for one of the next images 
is made.

Speed Tracer: 0.23

Chrome: 14.0.814.0 dev

What feature are you requesting?

A clean document or example code on web worker



What benefits would the feature provide?

It can be used more wildly other than only in speed tracer

Briefly describe any workarounds available:

Wait for the GWT team to do this. but I can't wait that day any more...

I wrote a sample, but doesn't work, any help will be appreciated

For Windows, the Speed Tracer pulls in a pre-built copy of python and puts it 
in src/third_party/third_party/python_2_4

Windows and Linux are left alone, but this makes the path references in our
python scripts fail. 

e.g.  stools/generate-event-record-type 

The workaround is to edit the script and update the path to python (or remove 
the explicit path and allow it to run from the PATH setting)

For one, make sure that google analytics ga.js cache durations are not 
flagged as a problem.

I have the Google Chrome Canary Build installed on my Windows 7 machine. 
Yesterday, I used speedtracer fine, today it doesn't work at all. I've 
attempted to uninstall/reinstall the extension, and the browser to no avail.

Steps to reproduce:
1. Install Google Chrome Canary build, 
(http://tools.google.com/dlpage/chromesxs)
2. Adjust link to include "--enable-extension-timeline-api" (My full shortcut 
looks like, "C:\path\to\Google\Chrome SxS\Application\chrome.exe" 
--enable-extension-timeline-api)
3. Install the speedtracer extension 
https://chrome.google.com/extensions/detail/ognampngfcbddbfemdapefohjiobgbdl
4. Open a website, and click on the extension.
5. White screen on extension. Javascript reports no errors, it just doesn't do 
anything

I don't see any network related hintlets firing.  Either speedtracer has been 
so influential that every web site has optimized themselves, or there is a bug 
in speedtracer hintlet processing.

Probably a bug related to the many changes in the timeline API network data 
format over the past year.

Provide a description of the buggy behavior observed:
Throws exception when getAllInWindow is called through an extension in chrome. 

What steps will reproduce the problem?
1. Write extension that Calls the method getAllInWindow.
2. Test extension.
3. Undefined method exception is thrown.

Give a description of the behavior you expected to see.
Should call method without error.

The build of Chrome you are using (check the About Chrome dialog)
Chromium 9.0.597.94 (Ubuntu 10.10)

What steps will reproduce the problem?
1. Go to a website.
2. Go back.
3. Go forward.
4. See duplicate entries in the network view for cached resources.

This is a Chromium devtools bug, not a Speed Tracer bug.
See: http://code.google.com/p/chromium/issues/detail?id=29076

Provide a description of the buggy behavior observed:

What steps will reproduce the problem?
call ImageLoader.loadImage(urls, callback)

Give a description of the behavior you expected to see.
callback.onImagesLoad(ImageHandle[] imageHandles)
imageHandles should contain array of handles in the same order as given by
urls argument.
Problem: all the handles contain information about image given by urls[0].

The version of Speed Tracer (check the chrome://extensions url)
SVN trunk (r48)

Problem in class com.google.gwt.graphics.client.ImageLoader:
51  public static void loadImages(String[] urls, CallBack cb) {
52    ImageLoader il = new ImageLoader();
53    for (int i = 0;i < urls.length;i++) {
54      il.addHandle(il.loadImage(urls[0]));
55    }
56    il.finalize(cb);
57    ImageLoader.imageLoaders.add(il);
58  }

Fix:
54      il.addHandle(il.loadImage(urls[i]));

Patch is attached to fix the issue.

I am getting the "Pfffttt, Speed Tracer is not working" message from recent 
unstable builds.  I am running on Ubunutu 11.04.

What steps will reproduce the problem?
1. Start a recent Chrome build (e.g. 14.0.835.0 dev) with the 
`--enable-extension-timeline-api` option.
2. Click the Speed Tracer extension icon
3. Wait a few seconds for Speed Tracer to attempt to start.

I expect no error message (and to be able to subsequently start a trace).

Instead, I get the Pffffft message as if I had not started Chrome with the 
command line switch.

Speed Tracer (by Google) - Version: 0.23

Google Chrome - 14.0.835.0 dev

This is the classic issue with SpeedTracer not running and simply responding 
"Pfffttt, Speed Tracer is not working." 

As for the two things listed to double-check: 
1. Yes, I am starting Chrome with the flag: --enable-extension-timeline-api

2. Yes, I am running dev channel, my Chrome version is 17.0.963.0 dev-m

After launching the dev version of Chrome (11.0.686.1 dev) with the 
ChromeWithSpeedTracer bootstrap (on OS X 10.5) the SpeedTracer extension fails 
to run.

What steps will reproduce the problem?
1. Install Chrome (11.0.686.1 dev).
2. Install SpeedTracer extension.
3. Launch ChromeWithSpeedTracer which launches Chrome browser.
4. Click on the SpeedTracer icon to right of url box.

Give a description of the behavior you expected to see.

Expect SpeedTracer window to launch and start to display stats about the 
currently loaded page.

Actual behavior is the SpeedTracer window opens with no stats. after a few 
seconds displays a warning dialog: No data received in 6 seconds. Chrome must 
be run with the flag: 
'--enable-extension-timeline-api'.
See getting started for more details.

Then when Chrome is exited the ChromeWithSpeedTracer process continues to run 
(confirmed by running top in Terminal). The only way to exit the 
ChromeWithSpeedTracer bootstrap is to `kill <process_id>`

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

The build of Chrome you are using (check the About Chrome dialog)
11.0.686.1 dev on OS X 10.5.8

Chrome version 7.0.503.0
The header in the network (resources) view are empty.

The version of Speed Tracer (check the chrome://extensions url)
0.17 and trunk

This looks like a Chromium bug as it works in early versions chrome with the 
same version of speedtracer.

Note: This is effects the integration with appstats. 

What feature are you requesting?

Pass a array from front page to the web worker in current 

speed tracer's GWT implementation?

Under some circumstance, it is not wise to convert array to

string to pass.


What benefits would the feature provide?

Huge ! 


Briefly describe any workarounds available:

 Pls, Pls not let me ask help from GWT team. :-) 

Currently it always opens in a new window. That's annoying.
I'd like it to open in a new tab.

It would be great to see an option where i can toggle whether the plugin should 
open itself in a new tab or in a new window.

P.S. maybe it even shouldn't be a plugin issue, but chrome browser issue.
There is no such tab/window option in chrome.
Yeah, by default it opens links in new tabs, but after using the browser for 
about two days i have countered about five-ten cases when pages are somehow 
opened in new windows and even middle-mouse-button doesn't help:( 

Provide a description of the buggy behavior observed:
When viewing the details of a particular event, the links to lines in the 
source code in stack trace don't appear to do anything. The links' src 
attribute is "javascript:;" if that's at all relevant.

What steps will reproduce the problem?
1. Record some events
2. Open the details of a particular event
3. Click on the "Line X:" link

Give a description of the behavior you expected to see.
I'd expect to be taken to the line being referred to.

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

The build of Chrome you are using (check the About Chrome dialog)
13.0.782.24

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

I have an application that does conditional requests using xmlhttprequests. 
Fiddler shows that the server answers with 304 (not changed) which means the 
resource is read from the cache, but Speedtracer shows return code 200 and "not 
cached".
This is with Chrome 7.0.517.17 dev on Windows XP. 
Speed tracer is the latest version from the web page. 

Speed Tracer (by Google) - Version: 0.14

In Netwrok resources tab, We have clicked on .png, Its showing summary, request 
header and response.
In summary: Its showing status code 200 and From cache false.

Here expected result should be 304 and not modified. 

Can you please explain if i am wrong. 

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

Please see details for Issue 43 at 
http://code.google.com/p/speedtracer/issues/detail?id=43
This issue's status is "fixed" but people are still experiencing the problem 
with the latest dev build and latest version of speedtracer.

Something changed recently in WebKit and we are now receiving records with 
negative time values. This needs to be investigated.

Yet another drawback of using the Chrome executable to package the 
speedtracer.crx is that on Linux, aside from having to specify chrome.path 
on the ant command line, you must have an X display running.  This is kind
of a pain in a continuous build environment (or like me building remotely)

build:
     [exec]
     [exec] (chrome:7433): Gtk-WARNING **: cannot open display:
     [exec] Result: 1

BUILD FAILED
/home/zundel/SpeedTracer/src/build.xml:40: The following error occurred 
while executing this line:
/home/zundel/SpeedTracer/src/client/build.xml:74: speedtracer.crx was not 
produced.


A workaround is to run Xvfb to create a virtual X display.