|
DevTools: log worker thread ids on the main thread when Timeline recording is enabled
DevTools uses TracingStartedInWorker trace event to figure out which worker threads correspond to the inspected page. The events were written on the worker thread which is racy. Current implementation always writes the event on the main thread. Since Tracing.start/end commands are handled on the main thread this eliminates racy behavior.
BUG= 401895, 405429
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=181820
Total comments: 7
|
Unified diffs |
Side-by-side diffs |
Delta from patch set |
Stats (+48 lines, -16 lines) |
Patch |
 |
M |
LayoutTests/FlakyTests
|
View
|
1
2
|
1 chunk |
+0 lines, -1 line |
0 comments
|
Download
|
 |
M |
LayoutTests/inspector/tracing/worker-events.html
|
View
|
1
|
1 chunk |
+2 lines, -2 lines |
0 comments
|
Download
|
 |
M |
LayoutTests/inspector/tracing/worker-events-expected.txt
|
View
|
1
|
1 chunk |
+2 lines, -2 lines |
0 comments
|
Download
|
 |
M |
Source/core/inspector/InspectorTraceEvents.h
|
View
|
1
|
2 chunks |
+6 lines, -0 lines |
0 comments
|
Download
|
 |
M |
Source/core/inspector/InspectorTraceEvents.cpp
|
View
|
1
|
2 chunks |
+9 lines, -0 lines |
0 comments
|
Download
|
 |
M |
Source/core/workers/WorkerInspectorProxy.cpp
|
View
|
1
|
2 chunks |
+2 lines, -6 lines |
0 comments
|
Download
|
 |
M |
Source/core/workers/WorkerThread.h
|
View
|
|
1 chunk |
+2 lines, -0 lines |
0 comments
|
Download
|
 |
M |
Source/core/workers/WorkerThread.cpp
|
View
|
1
2
|
1 chunk |
+7 lines, -0 lines |
0 comments
|
Download
|
 |
M |
Source/devtools/front_end/timeline/TracingModel.js
|
View
|
1
2
|
5 chunks |
+16 lines, -3 lines |
0 comments
|
Download
|
 |
M |
Source/devtools/front_end/timeline/TracingTimelineModel.js
|
View
|
1
2
|
2 chunks |
+2 lines, -2 lines |
0 comments
|
Download
|
Total messages: 16 (4 generated)
|