Memory management in One Commander

One Commander is made in Microsoft's .NET framework, which manages memory for One Commander. Windows may let a program's memory footprint grow while the program is used but when Windows needs memory again, it will compact the program memory and reclaim unused resources.
One Commander caches icons so they are loaded faster the next time they are needed in the program session. All displayed file properties are also cached while they are in the list, so scrolling through large folders will use more memory, but the memory will be released once the user opens another folder (at Windows' own schedule).
Each thumbnail in the file list and displayed preview will take a chunk of memory. For example, a previewed 10-Megapixel photo will take 10x3 Megabytes (3 as number of color channels), even if the image is a compressed jpeg.
Tabs don’t take additional memory in One Commander.
If you choose to keep the program running in the background on close (see the option in Settings > Window) all windows, file properties, previews and the rest will be unloaded from memory, but the program will keep cached icons and compiled code for a faster next start, while minimizing RAM usage.