Generally the bLength of a string descriptor should be an even number, since the strings are UTF-8 encoded. however, if the descriptor bLength was set incorrectly, the current protocol analyzer will produce an invalid unicode character for the last frame, and the frame end sample will also overlap with the CSC, as seen in Saleae ticket 98828.
This issue should only affect incorrect descriptors, and as of Logic 2.4.39, invalid unicode sequences no longer cause crashes in the data table, so the remaining priority of this issue is very low.
Generally the bLength of a string descriptor should be an even number, since the strings are UTF-8 encoded. however, if the descriptor bLength was set incorrectly, the current protocol analyzer will produce an invalid unicode character for the last frame, and the frame end sample will also overlap with the CSC, as seen in Saleae ticket 98828.
This issue should only affect incorrect descriptors, and as of Logic 2.4.39, invalid unicode sequences no longer cause crashes in the data table, so the remaining priority of this issue is very low.