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
The timeline view appears to incorrectly behave when the timeline it's configured with does not exist. Unfortunately, that's a very common situation:
run some logging script with a custom timeline
configure a dataframe view set on that custom timeline
run the logging script again
💥
In release build: 💥 == the dataframe view timeline switched to log_time
In debug build: 💥 == panic from a debug assert
What seem to happen is that when the 2nd recording is created but before the first data reaches the viewer, the dataframe view doesn't see the timeline it's configured for and incorrectly handle the situation.
This can be reproduced with the simplest of the script:
The timeline view appears to incorrectly behave when the timeline it's configured with does not exist. Unfortunately, that's a very common situation:
In release build: 💥 == the dataframe view timeline switched to
log_time
In debug build: 💥 == panic from a debug assert
What seem to happen is that when the 2nd recording is created but before the first data reaches the viewer, the dataframe view doesn't see the timeline it's configured for and incorrectly handle the situation.
This can be reproduced with the simplest of the script:
The text was updated successfully, but these errors were encountered: