Hi Divya,
Thanks for the reply. This issue has occurred on many different PCs (Windows 7 and Windows 10) and has stretched back at least 6 years across various versions of .NET Framework (3.5 to 4.5 to 4.7.2), Visual Studio (2015 to 2017 to 2022), and Infragistics (10.2 to 16.1 to 18.2).
But your questions made me review error logs from the past several years and in doing so I discovered that the issue occasionally affects our own DLLs as well, so this is not an Infragistics issue as I initially expected. As such my post can be disregarded.
Thanks again for your quick response.