Nothing Showing Up - Rails 3.1.6, Ruby 1.9.2p321


#1

Like the commenter here, I don’t see the profiler on the left after including the gem in my Gemfile.

Rails 3.1.6
Ruby 1.9.2p321
Rack 1.3.6

Gemfile: http://pastie.org/4337543


#2

I’ve got the same problem. I didn’t see any errors in either log or JS console or any non-application related requests in browser network log.

It’s interesting to note that when I add ?pp=help I see the instruction screen (as expected). The Rack::MiniProfiler is the first middleware in chain (again, as expected).

Using Rails 3.2.6, Ruby 1.9.3p194, Rack 1.4.1


#3

could this be a caching thing, can you try dumping your cache, is chrome network tab showing anything


#4

I dumped my cache, still nothing. The network tab doesn’t show anything related to mini profiler.

My Gemfile.lock is here: http://pastie.org/4360161


#5

Also, when I add pp=help, I don’t see the instruction screen.


#6

Can you see it in your middleware? Try running rack middleware what is the output?


#7

It’s completely working now. I guess I had to manually add it to config.ru. I really, really appreciate your taking the time to try to help me solve this!


#8

Another issue that came up really recently was a huge response header size causing the entire app to fail to load in Chrome: http://stackoverflow.com/questions/11872152/error-325-unknown-error. The X-MiniProfiler-Ids portion of the header was very very large.

May be similar to: http://code.google.com/p/mvc-mini-profiler/issues/detail?id=99


#9

Every refresh generated more information, so in the end, my response header was very, very big.


#10

I’m on the same project as Damir. I should note that our project is on Postgres, in case that makes a difference.


#11

can you include your Gemfile.lock, I suspect it may be cause of an old Rack version


#12

so the deadlocks stopped? they should not be happen, rack lock has som funny semantics about releasing its lock so I may have missed an edge case in an older rack gem


#13

keep in mind the rail tie should have hooked this up


#14

we NEED a sane limit for these header, can you raise a new one on it


#15

Not sure what you meant?


#16

I mean that it should be impossible to have a crazy number of unviewed ids in the header.