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
I believe this is due to one the libraries changing since the trace was captured. But we have encodings in the trace, so the view tool should not even bother trying to map the binaries.
A workaround is to point at the trace/ subdir if someone hits this before it's fixed.
The text was updated successfully, but these errors were encountered:
The view tool was blindly loading binaries even for traces that have
encodings. This leads to fatal errors when binaries have changed,
even when the change has no impact on viewing a trace. We fix that
here by reading the filtype at init time.
Tested locally where the view tool asserts without this fix.
Fixes#6940
When I create a trace and then rebuild auxiliary binaries I get a view tool assert:
I believe this is due to one the libraries changing since the trace was captured. But we have encodings in the trace, so the view tool should not even bother trying to map the binaries.
A workaround is to point at the trace/ subdir if someone hits this before it's fixed.
The text was updated successfully, but these errors were encountered: