File hash calculation based on libnss3 results in unacceptable packet drops ratio

Help
2

The call stack is as follows：

#8  0x0000fffff799e214 in nss_Init (configdir=0xfffff7ab4218 "", certPrefix=0xfffff7ab4218 "",
    keyPrefix=0xfffff7ab4218 "", secmodName=0xfffff7ab4218 "", updateDir=0xfffff7ab4218 "",
    updCertPrefix=0xfffff7ab4218 "", updKeyPrefix=0xfffff7ab4218 "", updateID=0xfffff7ab4218 "",
    updateName=0xfffff7ab4218 "", initContextPtr=0x0, initParams=0x0, readOnly=1, noCertDB=1, noModDB=1,
    forceOpen=1, noRootInit=1, optimizeSpace=1, noSingleThreadedModules=0, allowAlreadyInitializedModules=0,
    dontFinalizeModules=0) at nssinit.c:689
#9  0x0000fffff799ec08 in NSS_NoDB_Init (configdir=0x0) at nssinit.c:950
#10 0x00000000006745e4 in PostConfLoadedSetup (suri=0xa21cd8 <suricata>) at suricata.c:2771
#11 0x0000000000674c44 in SuricataMain (argc=5, argv=0xfffffffff388) at suricata.c:2957
#12 0x000000000048feec in main (argc=5, argv=0xfffffffff388) at main.c:22

Changing the 17th parameter(optimizeSpace) of nss_Init function to false can solve your problem