Home

John 3:16 For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.

 

Memory Fox Browser Add-on

Memory Fox 7.5.3
1. Added Auto-Restart when Working-Set memory has reached a set threshold in the Options dialog. This option only works with ( Activate Memory Fox – Browser Only ) mode.

2. Added the Firefox routine functions from about:memory to do the garbage collection automatically in conjunction with Memory Fox's memory recovery to farther reduce the virtual memory.

I've been beta testing newly discovered core API calls that I believe which have been causing dynamic increases in memory requirements. In my coming beta I'm introducing into Memory Fox an additional DLL injection to stop these API's from constantly increasing the need of memory beyond a normal browser session.

Supporting updates to the following browsers:

1. Firefox 6.0

2. Firefox 7.0 beta ( 2011-08-25 )

3. Aurora 8.0a2 (2011-08-25)

4. Nightly 9.0a1 (2011-08-25)

5. Pale Moon 6.0

Most browsers such as Google Chrome, IE9, Flock, Opera, Firefox will normally require an increase to the memory for the Virtual Paging and Physical Ram. You'll see this memory increased periodic by the constant refreshing of a web page dynamically by it's server or the addition of a new web page URL without any assistance of a memory reduction or recovery add-on. This action would also exclude any stand-alone external application aids as well. When Physical Ram memory reaches a limited accessible amount, a user will more than likely be introduced to an OS Blue Screen or a Memory Exception lockup freezing the system. The idea of Memory Fox as an add-on is to help service an increase of the amount of available Physical Ram memory to help foster the continuation of a browser's logged session including additional active applications. The Operating System Virtual Manager can handle the Virtual Paging effectively and efficiently. Observation of a speed variation by the browser during this memory recovery action or latency would become very noticeable, then it's time to upgrade the Operating System and/or hardware for proper browsing or stand-alone application usage, IMHO.

During the early development phase for Memory Fox I've discovered some API calls internally within the core of Firefox that would habitually cause an increase for the two types of memories, Virtual Paging and Physical Ram. I initially tried utilizing the coding within an XPCOM DLL to force a flushing of the Ram memory back to the Virtual Paging thereby having Firefox close some of the orphaned files and memory handles. This message action allowed me to post out to the Firefox.exe some additional API messages to halt this redundant action causing the increase. What a user would see is the Ram Memory being again filled in by the Virtual Paging Manager, and this being ONLY the valid and essential pages of information need at that current immediate time. This action would be without the inclusion of unnecessary obsolete data paging information that had been left abandon in Physical Ram. This operation action would seem to improve memory intermittently at times, so I moved the code out of the XPCOM add-on to an Out-Of-Process application as a stand-alone known as Memory Fox. Memory Fox would reduced the overhead of the Physical Ram which would indicate that it was successful by testing with the same Tabs Opened ( With ) and ( Without ) the aid of the Memory Fox add-on as being activated. Although, one could verify that there would be a normal increase in the Virtual Page memory, the idea was to increase as much as possible the available Physical Ram memory. The action would lessening the chances of a memory exception failure by providing a longer usage time for the Firefox browser session or allow other applications running parallel the same advantage.

Recently, in a new beta version of Memory Fox, I've injected a DLL to remove the offending API calls before they are consumed by supporting functions internal to the core Firefox code. There are many external coding layers of support for a browser application to function as a single executable unit. Problems with the memory issue is complicated by having to give attention to the Chrome, Gecko, Java Script, or Binary coding all the stuff that becomes the glue for the Firefox browser. Finally, this method by DLL injection process into Firefox has shown great promise toward limiting or stopping this habitual memory demand. The Memory Fox is still a FREE work in progress.

Memory Fox 7.4 Supported Browsers

Firefox-Logo-SmallMozilla Firefox

Pale Moon Logo  Pale Moon

Additional External Supported Browsers

Setting Memory Fox Options item 'Memory Recovery For All Running Application Processes'  allows support for the following windows browsers

John 3:16 For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.

Use Memory Fox 7.5.3 Reduce Ram Memory

Visit The Following Sites For More Information About Mozilla Firefox

Need Help with Firefox ?

Mozilla Add-ons Forum

mozillaZine

  • Twitter Firefox+Memory

    • @robmcguire Firefox sometimes uses more memory than it should. Try one of these easy fixes http://t.co/EVvtxCiD #fxhelp
    • Regained almost 1GB of memory simply by closing Firefox. It would be great if Mozilla ever got around to fixing that
    • Why is Firefox gobbling up my CPU & memory? It's making iTunes look brilliantly efficient.
    • All these years and Firefox is still a memory hog. Oy.
    • @andrea_r I mention it cause Firefox eats memory like one of those champion eaters :/
    • Has a lot of fire in it bro. Needs a lot to douse, you see! RT "@primaveron: Firefox is such a memory whore. 700MB of RAM. What for?!"
    • Firefox is such a memory whore. 700MB of RAM. What for?!
    • RT @abrahamvegh: Q: Photoshop, Illustrator, and Dreamweaver are running. What app is using the most memory? A: Trick question, it’s Firefox.