Commit Graph

3 Commits (18e5c8d4fb6d679cc71afa9a30d39d93accfb6dc)

Author SHA1 Message Date
Tor Lillqvist 18e5c8d4fb Try repeated async events with same name and id
Signed-off-by: Tor Lillqvist <tml@collabora.com>
Change-Id: Iddaf193f6daa0ba680a068b19b084df0f4422b73
2021-06-23 12:26:27 +03:00
Tor Lillqvist 18fe91c651 Add more variations of async events
Signed-off-by: Tor Lillqvist <tml@collabora.com>
Change-Id: I0ba63f6a7d062fe21646f8750d81f4189e8cfb19
2021-06-23 12:22:31 +03:00
Tor Lillqvist 4a95af2ac7 Add a small hand-crafted Trace Event file for checking how Chrome displays it
(See https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/preview#heading=h.jh64i9l3vwa1 )

Sadly, Chrome's chrome://tracing tool does not display the nestable
non-deprecated async b(egin) and e(nd) events at all. It does display
the non-nestable deprecated S(tart) and F(inish) events, though. Most
likely we can drop the support for the nestable async events in core
and here.

Signed-off-by: Tor Lillqvist <tml@collabora.com>
Change-Id: I7c3a05b265a83cef56e80a575df69d1b53c62278
2021-06-23 11:52:45 +03:00