GitHub PushEvent at 2014-12-29 23:25:11
Repository: blink-crosswalk
Actor: lincsoon
Payload: {"shas":[["9a766479fa52f2140361c1e0379b7cba1756a780","59cfc5d7ed3a03e88a52d98628b41643212e1f5f@intel.com","Chromium CPU profiler: source line support\n\nThis is the second and final part of adding source line support in Chromium CPU profiler that needs to be done to move XDK CPU profiler on the same way as CDT uses.\n\nIn brief, we need to do two things:\n1) Map the samples to source lines during profiling session and add new V8 public API to get the hit source lines. These changes are already merged into v8-crosswalk.\n2) The Chrome profilers works as follows: Chrome Browser ==(a \"start/stop profiling\" command)==> WebKit (WebSocket) ==> WebKit(InspectorBackendDispatcher) ==\"start/stop profiling\"==> WebKit(InspectorProfilerAgent) ==V8 Public APIs (StartProfiling/Stopprofiling)==> V8.\nSo, on StopProfiling command, WebKit(InspectorProfilerAgent) gets the collected results (using V8 public API) and packs them into JSON to send back to Chrome browser.\n\nThis patch implements writing info about the hit source lines in JSON data to be sent back to Chromium browser.\n(cherry picked from commit f16d9209f530d0ab2a2572f0679b14ea7d2f96dc)\n\nRe-enabling CPU profiling feature broken after migration to new v8.","Denis Pravdin",true],["ef7455cd2a78bb7f85f5d8356047daf658b1ce5a","b7f5c7b418c486227fed1e7e93a8ba75877793af@intel.com","The Chrome DevTools protocol part of the XDK\n\nin-depth allocation tracker\n\nThere are three new commands are added by analogy with Chrome DevTools\nallocation tracker. Start/Stop and Event which is sent by timer.\nCommand stopTrackingHeapXDK accepts three parameters: stack depth for unwinding,\nSample After Value - period of timer and a flag to collect retention\ninformation or not. Event sends to the host currently collected data about\nsymbols/callstack/objects. Command stopTrackingHeapXDK returns the final\ninfo witch is similar to Event passed format with one more parameter: duration\nof the collection.\n\nBasing on this info consumer can build allocation call tree for any period of\ntime, annotate source by self and total allocation mertics and annotate\nallocation call tree by the objects, which retain other objects in the memory","Andrey Malyshev",true]],"size":2,"ref":"refs/heads/master","head":"ef7455cd2a78bb7f85f5d8356047daf658b1ce5a"}