The Google-analytics example of a threaded analytics destination sleeps for an entire logging interval (30s in my case) in the destructor before closing. This probably works OK for most projects, but it is quite annoying when debugging and seems like it could cause problems when dumping final logs in a crash scenario. Is there any easy way to manually trigger a batch of events to send and close without this long pause?
Related Topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
|
[FR] ThreadedAnalyticsDestination - flushing events before closing
|
0 | 95 | January 3, 2024 | |
| Stopping a thread pool? | 10 | 658 | May 6, 2022 | |
| Thread doesn't exit cleanly, why? | 2 | 709 | April 17, 2017 | |
| ThreadedAnalyticsDestination data race | 2 | 222 | March 26, 2021 | |
| [Bug] Analytics Demo EXC_BAD_ACCESS when internet connection is flaky | 8 | 814 | April 30, 2018 |