Right now, when trying to deterministically create markers for csstriggers.com data, when we stop a recording, we may miss out on ~200ms worth of markers inbetween polling. We should drain all remaining markers. Started to hack on this, but it got a bit more complicated, as we immediately set the recording to not recording, which won't collect future marker events, etc. and the realtime markers makes this trickier than it should.
This issue has more to do with realtime recording rather than the start/stop recording in Bug 1408124
You need to log in before you can comment on or make changes to this bug.