Displaying incorrect delta time for display filtered data
After updating to 4.0.2 I have noticed that the "Time since previous displayed frame" is sometimes incorrect. Usually by many seconds when the actual delta should be milliseconds or less. For example, consider two display adjacent frames. Frame 149752 has an epoch time of 1672928416.072060000 and frame 150424 has an epoch time of 1672928416.996811000. However, frame 150424 reports a time delta from previous displayed frame of 159.926315000 seconds. < I would provide example screenshots, but apparently I am not allowed.>
Screenshots would be less than helpful as we'll probably require access to other fields. Can you publicly share a capture with the packets of interest?
Unfortunately, I am not able to share the capture. It contains proprietary data, both ours and our suppliers. I also tried to export the selected frames, but when opened in a new session, the delta time displayed properly. I also tried to export the specified frames along with the intervening frames. Again, the delta time displayed properly when using the same display filter. This example was just one of many in my capture that displayed incorrect deltas. The values were both positive and negative. Oddly, in the process of trying to see what would happen with a smaller subset for export, I changed the display filter from looking at "data.data contains XXXX and tcp.port == YYY" to a specific range of frames. When I went back to look at the full dataset with my prior display filter, the delta time values seem to be displaying proper values. This was ...(more)