Issue Description

After a long period of time continually streaming from my D435i (anywhere between 10 minutes and 5 hours), I find that the timestamps begin to be largely out of sync with the system clock.

The D435i uses a global time domain, which as far as I understand should sync time periodically with the device it's connected to. I notice that it does attempt to synchronize by adjusting frame timestamps by a few milliseconds, which I'm assuming is normal, occasionally during normal operation.

After anywhere between 10 minutes and 5 hours (typically around 2 hours) the timestamps are wildly different and jump 50 years into the future 🤖

I've modified the rs_callback example so you can reproduce what I've found, please let me know if I've done anything fundamentally wrong in that modified example.
rs-callback.txt

The log I produce from that example is as follows:
callback_rs3.log

I'm aware there's already an issue of global timestamps being erratic within the first 15 seconds (Global Timestamp: first 15 seconds of frames timestamps are unstable (DSO-12942)), so I'm ignoring any wrong timestamps within that time.

Let me know if there's any way I can workaround it in the meantime, maybe there's something I can do with my system clock. Perhaps an NTP server could interfere?