Commit 14bfcf7
committed
fix: ignore engine closed events for data track packets which are in flight / un delivered on engine close
I have noticed in running the data track end to end test, that "engine
closed" gets thrown fairly often.
I think the move away from the while/sleep loop in
waitForBufferStatusLow (which wasn't in my data track subscription
updates PR) has newly resulted in more waitForBufferStatusLow s being in
flight at once so there's a much higher likelihood that the data channel
won't be drained upon engine close.
To fix this, I've added a param to waitForBufferStatusLow to allow
ignoring engine closed events. Not sure if this is the best thing to do
but it fixes the tests, and I think matches the ethos of "send packets
as fast as possible" / doesn't introduce any sort of explicit locking.1 parent 6696692 commit 14bfcf7
1 file changed
Lines changed: 9 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1519 | 1519 | | |
1520 | 1520 | | |
1521 | 1521 | | |
1522 | | - | |
| 1522 | + | |
1523 | 1523 | | |
1524 | 1524 | | |
1525 | 1525 | | |
| |||
1580 | 1580 | | |
1581 | 1581 | | |
1582 | 1582 | | |
1583 | | - | |
| 1583 | + | |
| 1584 | + | |
| 1585 | + | |
| 1586 | + | |
1584 | 1587 | | |
1585 | | - | |
| 1588 | + | |
1586 | 1589 | | |
1587 | 1590 | | |
1588 | 1591 | | |
| |||
1593 | 1596 | | |
1594 | 1597 | | |
1595 | 1598 | | |
1596 | | - | |
| 1599 | + | |
| 1600 | + | |
| 1601 | + | |
1597 | 1602 | | |
1598 | 1603 | | |
1599 | 1604 | | |
| |||
0 commit comments