tree c1c6c1c39f2bf826959b53b996ee715ae91c25f4
parent da87520b03467ddcec71daedcb48cfd70b13928e
author ssid <ssid@google.com> 1563909319 -0700
committer ssid <ssid@google.com> 1563909319 -0700

Order the trace writer while commiting in startup registry

If the trace buffer size is smaller than the size in startup registry
then we end up with events with a few random threads. To avoid this,
bind the trace writer in order of creation, and keep all writers
waiting if any bind call fails. This would make it more likely to get
chunks from writers in order.
Ideally we should order chunks in order of commit, but it is lot of
information to keep track.

Change-Id: I9bb492aa286d663df7f7de32688aec412023ef6f