fixing greasemonkey scripts for current version of firefox

#FIXING GREASEMONKEY SCRIPTS FOR CURRENT VERSION OF FIREFOX INSTALL#
#FIXING GREASEMONKEY SCRIPTS FOR CURRENT VERSION OF FIREFOX WINDOWS#

KoC Power Bot is a much more efficient framework and it is the next evolution in KoC scripts. This needs to be fixed, but it doesn't seem like a release blocker to me.The KoC Scripters team (which includes a number of other programmers as well as myself) have now finished moving all of the most useful features of this script into KoC Power Bot, so I have decided to retire KoCAttack Extra for now. Step 9 through 18, but repeat 14 on every tab, I still get the same one(/two)Ĭompartment left over, not one(/two) per tab. If I start step 9 (restart) throughġ8, but skip step 14 (open the menu), all the compartments go away.

#FIXING GREASEMONKEY SCRIPTS FOR CURRENT VERSION OF FIREFOX INSTALL#

(Is there a better thing to say for this? I keep getting updates on theīeta channel but it's always '15.0' - which version of 15.0 is it?'ĥ) Install 1.0beta7 from the development channel at the bottom.ġ0) Navigate the only open (about:home) tab to about:compartmentsġ1) There's tons of system compartments user compartments says only about:homeġ2) More verbose shows lots more data in system empties user.ġ4) Open the Greasemonkey menu to see it has theġ7) Switch to the first (about:compartments) tab, press F5ġ9) Close the right-most tab, press F5, user compartments now says:Ģ0) Close the right-most tab, press F5, user compartments now says:Ģ1) Close the right-most tab (only one left, about:compartments, now),

(I keep the beta channel firefox around for development, this is FF 15.) Details Ok, time to be even more careful and explicit:ġ) 'cd' to my test profile directory rm -rf *Ģ) ~/opt/firefox-dev/firefox -no-remote -P test Output of about:memory with verbose on, at point mentioned in the comment │ │ │ ├──23.48 MB (01.85%) ── uncompressed-heapĢ3.48 MB ── images-content-used-uncompressedĢ5.12 MB ── js-main-runtime-analysis-temporaryĢ60.28 MB ── js-main-runtime-gc-heap-allocatedġ32.99 MB ── js-main-runtime-gc-heap-arena-unusedĠ.00 MB ── js-main-runtime-gc-heap-chunk-clean-unusedĠ.00 MB ── js-main-runtime-gc-heap-chunk-dirty-unusedģ93.27 MB ── js-main-runtime-gc-heap-committedġ32.99 MB ── js-main-runtime-gc-heap-committed-unusedĥ1.09% ── js-main-runtime-gc-heap-committed-unused-ratioĢ0.73 MB ── js-main-runtime-gc-heap-decommittedģ0.07 MB ── js-main-runtime-type-inferenceĠ.04 MB ── window-objects-layout-pres-contextsĠ.46 MB ── window-objects-layout-style-setsĠ.00 MB ── window-objects-layout-text-runs

#FIXING GREASEMONKEY SCRIPTS FOR CURRENT VERSION OF FIREFOX WINDOWS#

In proper working, there should be no ghost windows that correspond to the closed tabs. Step 9 and 10 show the signs of a memory leak.

Notice that the Ghost windows count will be a non-zero value (it should be zero!).ġ0- Goto about:compartments and refresh the page and notice the ghost windows that exist for all links opened in step 7. > confirm this? There's been enough back and forth that I'd prefer verbosityĢ- Install latest Greasemonkey (0.9.22) from the Addons websiteĤ- Install 'Textarea backup with expiry' from ħ- Open the following links in separate tabs:ĩ- Goto about:memory and hit 'Minimize memory usage' few times. > Can you give me some idiot-simple steps to follow and signs to look for to

> I am currently using the latest Firefox 15 beta, and GM 0.9.22, and the leaks are still happening. (In reply to Anthony Lieuallen from comment #52)

Fixing greasemonkey scripts for current version of firefox