Memtrace notices when two consecutive backtraces share a long prefix and doesn't encode the prefix twice. However, since very long backtraces are truncated, it is possible in some cases to have a shared prefix that is longer than the untruncated portion. This triggered an assertion failure in the reader, fixed by this patch.
(This is a reader-only fix, so should make traces that hit this bug become readable without changes)
Memtrace notices when two consecutive backtraces share a long prefix and doesn't encode the prefix twice. However, since very long backtraces are truncated, it is possible in some cases to have a shared prefix that is longer than the untruncated portion. This triggered an assertion failure in the reader, fixed by this patch.
(This is a reader-only fix, so should make traces that hit this bug become readable without changes)