Loading a large brsar file can sometimes cause a System.OutOfMemoryException (which can be alleviated by moving to 64-bit, but that's not what this issue is about)
when this has occurred, all the memory that's been loaded remains there and doesn't get released, leading to more OutOfMemoryExceptions when opening smaller files that are normally able to be opened fine.
Loading a large brsar file can sometimes cause a System.OutOfMemoryException (which can be alleviated by moving to 64-bit, but that's not what this issue is about) when this has occurred, all the memory that's been loaded remains there and doesn't get released, leading to more OutOfMemoryExceptions when opening smaller files that are normally able to be opened fine.