You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit bbf88aa
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ios-runner): bound recorder frame capture through runMainThreadWork
A recording tick captured its frame with an unbounded DispatchQueue.main.sync
on the recorder queue. While the main thread was wedged the first tick
blocked the recorder queue, and the busy and wedged accounting never saw it.
Each tick after the bootstrap frame now hops to main through
runMainThreadWork with a timeout of one frame interval, on iOS and macOS.
A capture that times out drops the frame and counts as abandoned work; its
late result is discarded and never appended. While any abandoned main-thread
work is outstanding the tick is skipped, so the recorder keeps at most one
capture pending on main. The bootstrap frame is still taken on the calling
thread, and screenshots keep their on-main capture path.
Closes#2801
0 commit comments