I've had a big bug caused by this module.
I've installed it and desintalled it and there was no doubt it was drupal for firebug causing the bug.

My bug was
The managed field page of one of my content type was inacessible (very slow request).
It was also the case for the context ui page, which could succeed showing the page but after a very long page.

Comments

frob’s picture

Status: Active » Closed (works as designed)

The way this module works is by exposing the array tree for nodes, pages, users, views, form, and (if enabled) all sql requests generated by the page load. This happens on every http (page) request. As such it adds a-lot of overhead to the page loads.

This module is not meant to be used on production sites, it is a development module.

fluxline’s picture

Issue summary: View changes

just to note, this also slows down views_ui a lot. understandable as a dev tool, but there should be a warning on the module page so people are aware.

frob’s picture

Category: Bug report » Feature request

Since this was works as designed it isn't really a bug.

This is noted on the Drupal project page. I don't think it is a good idea to over notice people.

fluxline’s picture

it is noted that it is for development purposes, the only addition i was suggesting is the slowdown that it can cause in some unexpected areas. for example, views_ui jumps to about 30 seconds to load a view or change a display edit. with that kind of delay, it's easy to get distracted from your work when using a computer, pron being an example.

you're right, it's not a bug...and it's not critical.