When you try to import/export/save a file in Didger and you get a message that you are out of memory, this is generally because your computer is truly out of memory. There are a couple things you can try to get around this error:
- Make sure you have the 64-bit version of Didger installed. The 64-bit version is able to access more memory than the 32-bit version.
The 32-bit versions of Didger are limited to the Windows maximum amount of memory. The maximum amount of memory that Windows can allocate to a 32-bit program is 2 GB. In addition, Windows typically reserves half the RAM for the operating system, so the available memory can be much less, regardless of the amount of RAM and size of your swap file. For example, if you have 2 GB of RAM, only a maximum of 1 GB can be used for Didger.
- Didger requires a contiguous block of memory. The computer may have enough free available memory to save/import/export the file, but if it is fragmented over several blocks, then Didger can only use the largest block of memory available. If you believe you have enough RAM to save/import/export the file, reboot the computer to defragment the memory, close down as many running applications as possible, and then try to save/import/export the file.
- Didger may be holding memory for the number of Undo levels you have set for Didger. If you have the number of Undo levels set to 15, then Didger has to hold the necessary memory to be able to undo the previous 15 actions. If they are actions that take a lot of memory, then Didger has to hold onto the same amount of memory it took to perform the actions so it can undo them. Restarting Didger resets the Undo actions so Didger can release the memory it was holding. Another option is to set the number of Undo levels to 0 or some other smaller number, so Didger can release some more memory. You can set the number of Undo levels by going to Tools | Project Settings.
Updated November 28, 2017