- On the Cleanmem support forum there was a similar OOM problem as well. But Cleanmem wasn't causing the problem.
http://forums.pcwintech.com/index.php/topic,5440.0.htmlAs said in this thread Cleanmem only reduces the "In Use" part of the memory, that part is turned into "Modified". (See "Resource Monitor", memory tab) and from there Windows takes over.
- Some programs can be a REAL "Pain in the a**". I came across a 32 bit program that was run on a 64 bit system with 12 GB of memory but the program would crash when it reached the upper limit of only 4 GB (the memory limit of a 32 bit system).
- I have a backup program to back up my HD but after having used that program my system has turned into one giant snail. Turns out that the file cache was VERY large (GBs) and occupied the entire memory (and more ???). Cleanmem "kills the snail" by collapsing the file cache.
- When I read the info on "Flushmem" then it looks like that this program uses a very different way of "cleaning caches", i.e. allocating as much memory as possible. That means "Flushmem" uses the "SetWorkingSet" API instead of the "EmptyWorkingSet" API. Using "SetWorkingSet" is what causes "a hiccup". No wonder, "Flushmem" can/will cause large problems.