RESOLVED FIXED 104545
Web Inspector: Profiler: split "getProfile" to "getCPUProfile" and "loadHeapSnapshot"
https://bugs.webkit.org/show_bug.cgi?id=104545
Summary Web Inspector: Profiler: split "getProfile" to "getCPUProfile" and "loadHeapS...
Eugene Klyuchnikov
Reported 2012-12-10 06:15:28 PST
This change will allow stronger typing of profiler output.
Attachments
Patch (15.52 KB, patch)
2012-12-10 06:22 PST, Eugene Klyuchnikov
yurys: review+
Patch (15.52 KB, patch)
2012-12-14 07:55 PST, Eugene Klyuchnikov
no flags
Patch (15.65 KB, patch)
2012-12-20 00:33 PST, Eugene Klyuchnikov
no flags
Patch (15.65 KB, patch)
2013-01-16 22:12 PST, Eugene Klyuchnikov
no flags
Eugene Klyuchnikov
Comment 1 2012-12-10 06:22:45 PST
Pavel Feldman
Comment 2 2012-12-14 00:28:36 PST
Comment on attachment 178532 [details] Patch @yurys, do you want to review this?
Yury Semikhatsky
Comment 3 2012-12-14 02:11:56 PST
Comment on attachment 178532 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=178532&action=review > Source/WebCore/inspector/Inspector.json:3035 > + "name": "loadHeapSnapshot", I'd name it getHeapSnapshot to avoid confusion with loading from filesystem and for consistency with getCPUProfile.
Yury Semikhatsky
Comment 4 2012-12-14 02:18:17 PST
This change will likely break chrome/test/pyautolib/remote_inspector_client.py and related automation tests. We should update the script when this change is committed and rolled.
Eugene Klyuchnikov
Comment 5 2012-12-14 07:54:00 PST
Comment on attachment 178532 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=178532&action=review https://code.google.com/p/chromium/issues/detail?id=166160 >> Source/WebCore/inspector/Inspector.json:3035 >> + "name": "loadHeapSnapshot", > > I'd name it getHeapSnapshot to avoid confusion with loading from filesystem and for consistency with getCPUProfile. Done.
Eugene Klyuchnikov
Comment 6 2012-12-14 07:55:58 PST
Eugene Klyuchnikov
Comment 7 2012-12-17 00:31:00 PST
(In reply to comment #4) > This change will likely break chrome/test/pyautolib/remote_inspector_client.py and related automation tests. We should update the script when this change is committed and rolled. Patch: https://chromiumcodereview.appspot.com/11583002/ CrBug: http://code.google.com/p/chromium/issues/detail?id=166160
Eugene Klyuchnikov
Comment 9 2012-12-20 00:33:10 PST
Created attachment 180290 [details] Patch rebased
Eugene Klyuchnikov
Comment 10 2013-01-16 22:12:41 PST
WebKit Review Bot
Comment 11 2013-01-17 10:52:25 PST
Comment on attachment 183120 [details] Patch Clearing flags on attachment: 183120 Committed r139998: <http://trac.webkit.org/changeset/139998>
WebKit Review Bot
Comment 12 2013-01-17 10:52:29 PST
All reviewed patches have been landed. Closing bug.
Ryosuke Niwa
Comment 13 2013-01-23 20:05:19 PST
This patch broke LeaksViewer :( Now we're getting erros like: Uncaught TypeError: Object #<Object> has no method 'getProfile'
Ryosuke Niwa
Comment 14 2013-01-23 20:11:29 PST
Reverted the change in http://trac.webkit.org/changeset/140639 since the Leaks Viewer pulls in the inspector code at r80565.
Eugene Klyuchnikov
Comment 15 2013-01-23 20:36:41 PST
(In reply to comment #14) > Reverted the change in http://trac.webkit.org/changeset/140639 since the Leaks Viewer pulls in the inspector code at r80565. I think that LeaksViewer should be fixed, as it was done with leaks-finder https://codereview.chromium.org/11615021/ Reverting this change you broke leaks-finder!!!
Ryosuke Niwa
Comment 16 2013-01-23 20:42:46 PST
Another fixed landed in http://trac.webkit.org/changeset/140641. (In reply to comment #15) > (In reply to comment #14) > > Reverted the change in http://trac.webkit.org/changeset/140639 since the Leaks Viewer pulls in the inspector code at r80565. > > I think that LeaksViewer should be fixed, as it was done with leaks-finder https://codereview.chromium.org/11615021/ > > Reverting this change you broke leaks-finder!!! Why is this random Chromium tool depending on Tools/BuildSlaveSupport/build.webkit.org-config/public_html/LeaksViewer/? Also, we can't break WebKit tool in order to fix Chromium tools. That's just not how it works.
Eugene Klyuchnikov
Comment 17 2013-01-23 20:45:37 PST
leaks-finder do not depend on LeaksViewer, it depend on inspector protocol.
Ryosuke Niwa
Comment 18 2013-01-23 20:51:14 PST
(In reply to comment #17) > leaks-finder do not depend on LeaksViewer, it depend on inspector protocol. Then nothing is broken.
Eugene Klyuchnikov
Comment 19 2013-01-23 20:58:18 PST
(In reply to comment #18) > (In reply to comment #17) > > leaks-finder do not depend on LeaksViewer, it depend on inspector protocol. > > Then nothing is broken. This patch contains changes to inspector protocol. All references to "getProfile" in this patch were replaced with "getCPUProfile" and "loadHeapShapshot". WebinspectorShims contains something that simulates WebInspector. This was also changed to conform new interface. The actual problem is: why LeaksViewer uses pulls web inspector code at r80565 and WebinspectorShims code at tip-of-tree?
Ryosuke Niwa
Comment 20 2013-01-23 21:05:43 PST
(In reply to comment #19) > (In reply to comment #18) > > (In reply to comment #17) > > > leaks-finder do not depend on LeaksViewer, it depend on inspector protocol. > > > > Then nothing is broken. > > This patch contains changes to inspector protocol. It does not! Did you even look at the changesets? All changes were made to: Tools/BuildSlaveSupport/build.webkit.org-config/public_html/LeaksViewer/WebInspectorShims.js
Eugene Klyuchnikov
Comment 21 2013-01-23 21:07:20 PST
(In reply to comment #20) > (In reply to comment #19) > > (In reply to comment #18) > > > (In reply to comment #17) > > > > leaks-finder do not depend on LeaksViewer, it depend on inspector protocol. > > > > > > Then nothing is broken. > > > > This patch contains changes to inspector protocol. > > It does not! Did you even look at the changesets? All changes were made to: > Tools/BuildSlaveSupport/build.webkit.org-config/public_html/LeaksViewer/WebInspectorShims.js Ooops. I'm really deeply sorry! Thank you for your assistance.
Note You need to log in before you can comment on or make changes to this bug.