Thanks for your bug report. If you can provide a minimal script similar to the one that is causing the issue, ie. uses a similar size hash table, file sizes, identical switches for the commands/identifiers, etc., I will test it out here. It doesn't matter at this point if it doesn't reliably reproduce the issue for you, I just need a starting point that matches the sequence of steps/commands/identifiers/switches/options that you are using. It may be that the debugger will catch something not immediately visible in a release version.

Last edited by Khaled; 03/08/22 11:23 AM.