Home

“Typical Memory Fox Activity”
http://idevfh.com/wp-content/uploads/2010/06/Exam0.jpg

“Memory Fox” is a successor to “AFOM 2.0″ providing a greater extension to memory recover and retention with both providing the same objective as stated below. “AFOM 2.0″ is loaded as a DLL to all instances of the Firefox browser. “Memory Fox” is provided as an external application not co-dependent on the Firefox browser. 

Requirements: Firefox 3.*.* Desktops or Laptops Computer with support for Windows XP , Windows VISTA , Windows 7 operating systems.
Note: “Memory Fox” is ( Windows ) only add-on

When Memory Fox is activated from Firefox, a user can choose to run in Mode 1 or Mode 2 operations of “Memory Fox”.  When using Mode 2, with Global Process checked, other application processes like that of TweetDeck, Seesmic and browsers such as Chrome, Flock, and Opera. These applications processes will  be included in the Primary and Secondary memory recovery operations. ( See Options Dialog ) of the memory recovery and retention process. Memory Fox, will help aid in reducing your current RAM overhead for other applications, hopefully, to have an opportunity to run within your system’s environment.

Objective: Whenever possible, Memory Fox, will provide dynamic ram memory recover, and will attempt to reduce and provide retention as an application’s resource demand.

This support is conducted by providing an external observer to  assist in the retention of an application’s hosting memory requirements of the System Ram and Virtual Memory Pages overhead.

“Memory Fox”, focuses on two ( 2 ) types of memory usage and with flushing for memory recovery. When resource requirements ( Stack and Heap ) have been reached, according to the user’s preset option settings, the memory will be flushed and recovered from Fragmented Orphaned ram memories.

Below are the two types supported for recovery.
1. Working Set: The set of memory pages currently visible to the process and is [ Shareable ] between other processes.

2. Private Working Set: The set of memory pages currently visible to the process and is [ Non Sharable ] between other processes.

Note 1: Commit Memory: The amount of virtual memory that is reserved for use by a process. Virtual pages of memory within this Commit Memory will be brought into primary RAM due to process demand. Commit Memory will change due to Files Open/Closed respectfully.

Note 2: “Memory Fox” has very low and minimum ( CPU ) Process duration requirement within Firefox when memory recovery action is performed.

Note 3: The following is a simple and brief description of a typical browser session’s while hosting an Internet connection and its user’s activities:If you monitor the browser’s process memory allocations, you’ll see that there will be a ( Rise/Fall ) of RAM ( Working Set ) and Virtual Memory ( Commit ) allocations fluctuate frequently.

Some web pages, independent of the user personal action, will make a dynamic request over the Internet to refresh content or add additional resource content to the web page. First, this action forces the browser to respond by providing additional memory resource space. Secondly, there could be the adding of an additional tabbed web pages, requiring the browser to response for the need to supply additional virtual pages per request to Virtual Memory Manager.

Now, with the above stated, “Memory Fox” does NOT use any API calls that would insert additional virtual pages to the ( Commit ), contrary to some beliefs. Most likely a user is seeing what I’ve described above. You can monitor this activity I’ve described ( With / Without ) “Memory Fox” being used.

Please report any “Memory Fox” working issues to:  idevfh@gmail.com