Slow-reports is ship back to our server with a chrome trace when some jank is detected on the chrome main thread.

In some case, the jank seems to be multiple seconds. See attachment.

Slow-reports (crash server)
    38b24142f4540d03    windows    69.0.3486.0    12 sec
    05a5695d2dab9c05    windows    67.0.3371.0    10 sec
    a4dd5b53755509a6    windows    69.0.3495.0     3 sec

The culprit function is DragHostMsg_StartDragging.

This is pointing to this code:
  https://cs.chromium.org/chromium/src/content/browser/renderer_host/render_widget_host_impl.cc?type=cs&sq=package:chromium&g=0&l=1810


My hypothesis is that some expensive computation is hidden behind
  1) for (const auto& file_info : drop_data.filenames) {
  2) for (size_t i = 0; i < drop_data.file_system_files.size(); ++i) {


 

Deleted: jank.png 27.1 KB

	jank.png 27.1 KB View Download

Slow-reports is shipping back to our server with a chrome trace when some jank is detected on the chrome main thread.

In some case, the jank seems to be multiple seconds. See attachment.

Slow-reports (crash server)
    38b24142f4540d03    windows    69.0.3486.0    12 sec
    05a5695d2dab9c05    windows    67.0.3371.0    10 sec
    a4dd5b53755509a6    windows    69.0.3495.0     3 sec

The culprit function is DragHostMsg_StartDragging.

This is pointing to this code:
  https://cs.chromium.org/chromium/src/content/browser/renderer_host/render_widget_host_impl.cc?type=cs&sq=package:chromium&g=0&l=1810


My hypothesis is that some expensive computation is hidden behind
  1) for (const auto& file_info : drop_data.filenames) {
  2) for (size_t i = 0; i < drop_data.file_system_files.size(); ++i) {


 

Deleted: jank.png 27.1 KB

	jank.png 27.1 KB View Download

Slow-reports is shipped back to our server with a chrome trace when some jank is detected on the chrome main thread.

In some case, the jank seems to be multiple seconds. See attachment.

Slow-reports (crash server)
    38b24142f4540d03    windows    69.0.3486.0    12 sec
    05a5695d2dab9c05    windows    67.0.3371.0    10 sec
    a4dd5b53755509a6    windows    69.0.3495.0     3 sec

The culprit function is DragHostMsg_StartDragging.

This is pointing to this code:
  https://cs.chromium.org/chromium/src/content/browser/renderer_host/render_widget_host_impl.cc?type=cs&sq=package:chromium&g=0&l=1810


My hypothesis is that some expensive computation is hidden behind
  1) for (const auto& file_info : drop_data.filenames) {
  2) for (size_t i = 0; i < drop_data.file_system_files.size(); ++i) {


 

Deleted: jank.png 27.1 KB

	jank.png 27.1 KB View Download