Buildbot crash output: fuzz-2020-11-05-24267.pcap

Problems have been found with the following capture file:

https://www.wireshark.org/download/automated/captures/fuzz-2020-11-05-24267.pcap

stderr:

Input file: /home/wireshark/menagerie/menagerie/xrite-i1displaypro-argyllcms-1.9.2-spotread.pcapng

Build host information:
Linux build6 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.5 LTS
Release:	18.04
Codename:	bionic

Buildbot information:
BUILDBOT_WORKERNAME=fuzz-test
BUILDBOT_BUILDNUMBER=20
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_URL=https://buildbot.wireshark.org/wireshark-3.4/
BUILDBOT_REPOSITORY=git@gitlab.com:wireshark/wireshark.git
BUILDBOT_GOT_REVISION=a00ac1eb9c391f887b3dd56a2c5508ec382790ce

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit a00ac1eb9c391f887b3dd56a2c5508ec382790ce
Author: Pau Espin Pedrol <pespin@sysmocom.de>
Date:   Tue Nov 3 20:01:32 2020 +0000

    rlcmac: Handle properly LI=0 in GPRS data blocks and identify spare bits
   
    The previous handling of LI=0 was a confusion with the LI=0 meaning from
    EGPRS (see TS 44.060 B.8.2 Example 2) data block.
   
   
    (cherry picked from commit 9d5de22a88b9cbd01e9f16953b2e372835d3d0d6)


Command and args: ./tools/valgrind-wireshark.sh -b /home/wireshark/builders/wireshark-3.4-fuzz/fuzztest/install.plain/bin 
==28634== Memcheck, a memory error detector
==28634== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==28634== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==28634== Command: /home/wireshark/builders/wireshark-3.4-fuzz/fuzztest/install.plain/bin/tshark -nr /fuzz/buildbot/fuzztest/valgrind-fuzz-3.4/fuzz-2020-11-05-24267.pcap
==28634==
==28634==
==28634== HEAP SUMMARY:
==28634==     in use at exit: 317,334 bytes in 30,885 blocks
==28634==   total heap usage: 415,654 allocs, 384,769 frees, 44,723,059 bytes allocated
==28634==
==28634== LEAK SUMMARY:
==28634==    definitely lost: 276,129 bytes in 30,681 blocks
==28634==    indirectly lost: 0 bytes in 0 blocks
==28634==      possibly lost: 0 bytes in 0 blocks
==28634==    still reachable: 40,410 bytes in 173 blocks
==28634==         suppressed: 795 bytes in 31 blocks
==28634== Rerun with --leak-check=full to see details of leaked memory
==28634==
==28634== For counts of detected and suppressed errors, rerun with: -v
==28634== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Definitely + indirectly (276129 + 0) exceeds max (102400).

no debug trace