May be I am just misusing the tool, but I feel like this is a bug:

So I profile an app, I filter the main thread and look at the flame graph and get this (which looks wrong):

I then select a range in the timeline view (a very useful feature btw, thanks a lot f

When running flamegraph its moaning about not having debug info even though its set in the cargo.toml and i also see it in the compile status output.

The docs say that ReactPerformance.createNotifier() returns a "middleware", but it actually creates a Redux store enhancer instead, which is why it needs to be passed to compose() instead of passed to applyMiddleware(). This should be fixed for clarity.

Can someone help with this?
{code}
$ protractor-perf protractor-perf.conf.js
[13:17:08] I/direct - Using ChromeDriver directly...
[13:17:08] I/launcher - Running 1 instances of WebDriver
Started
Here
F

Failures:

1. angularjs homepage todo list should add a todo
   Message:
   Failed: [logTypes()] Not JSON response
   Stack:
   Error: [logTypes()] Not JSON response
   at export

@daveshah1 has some pretty nice up5k demos at https://github.com/daveshah1/up5k-demos/tree/master

As we really care about the up5k, it seems like a good idea to add these demos to the perf tool.

• explain how to display summary on node exit
• add require('perf-logger') at beginning to be more explicit about how to require