Hello @rahul,
It seems that browser has not full support of PerformanceTiming
API and attaches incorrect instance of its context.
I created a ticket to investigate this.
Until it is resolved you have several options:
- Disable
PerformanceTiming
- Recover bad rows using Event Recovery
How many events are going to bad bucket with this error? I believe this should be extremely small.