Wrong calculation of number of QUIC packets in Protocol Hierarchy window - bug
Summary
Simply: Number of captured frames cannot be lower then number of QUIC packets, but Wireshark statistics claims it.
Steps to reproduce
Capture any QUIC traffic while running Chrome and openning some webpage that supports IETF QUIC, google sites, for instance.
What is the current bug behavior?
When you capture traffic and there is a QUIC (IETF) over UDP connection, you get strange results in Protocol Hierarchy Statistics window. Please see example printscreen. QUIC protocol was selected to be displayed and there is obviously 100% of Ethernet frames (242 packets), however, in case of QUIC, Wireshark displays total of 243 packets (100.4%). It doesn't make sence, because QUIC is encapsulated in Ethernet / IP / UDP. Similar problem appears for QUIC over IPv4 or IPv6, or also when not using "quic" display filter.
What is the expected correct behavior?
Number of QUIC packets should be always lower or equal to number of captured Ethernet frames. Number of QUIC packets should be also lower or equal to number of captured UDP or IP packets.
Sample capture file
Sample capture provided as attachement.quic-small-traffic.pcapng
Relevant logs and/or screenshots
Build information
Version 3.6.3 (v3.6.3-0-g6d348e4611e2)