It is possible to disable developer extras without disabling profiling. This leads to an assertion failure in JSDOMWindowBase.cpp. ASSERT(enabled || !supportsProfiling(thisObject)); from IRC: [17:04:06] <olliej> kpiascik: technically the assertion isn't harmful, but it wil mean poor performance and poor memory usage We should disable profiling when the front-end is detached.
Created attachment 122420 [details] patch
Comment on attachment 122420 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=122420&action=review > Source/WebCore/inspector/InspectorController.cpp:236 > + disableProfiler(); You should call disable() from within InspectorProfilerAgent::clearFrontend() instead.
Created attachment 122427 [details] updated patch
Comment on attachment 122427 [details] updated patch Clearing flags on attachment: 122427 Committed r104945: <http://trac.webkit.org/changeset/104945>
All reviewed patches have been landed. Closing bug.