Magic-Mirror/gecko-dev
1
0
Fork 0
mirror of https://github.com/mozilla/gecko-dev.git synced 2025-02-21 17:59:34 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Make leak-gauge.html not require enhanced privileges. b=414800

Browse Source
This commit is contained in:
dbaron@dbaron.org 2008-02-08 11:55:34 -08:00
parent 84ad3b01d3
commit 175d7bdddf
1 changed files with 29 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

66
tools/footprint/leak-gauge.html
View File

@ -48,9 +48,7 @@ pre.output { border: medium solid; padding: 1em; margin: 1em; }
</style>
<script type="text/javascript">
function run() {
var result = "";
function runfile(file) {
// A hash of objects (keyed by the first word of the line in the log)
// that have two public methods, handle_line and dump (to be called using
// call, above), along with any private data they need.
@ -238,30 +236,15 @@ function run() {
}
};
netscape.security.PrivilegeManager.enablePrivilege("UniversalXPConnect");
const cs = Components.classes;
const ifs = Components.interfaces;
var filePicker = cs["@mozilla.org/filepicker;1"].
createInstance(ifs.nsIFilePicker);
filePicker.init(window, "Select NSPR Leak Log", ifs.nsIFilePicker.modeOpen);
if (filePicker.show() != ifs.nsIFilePicker.returnOK)
return;
var is = cs["@mozilla.org/network/file-input-stream;1"].
createInstance(ifs.nsIFileInputStream);
const PR_RDONLY = 0x01;
is.init(filePicker.file, PR_RDONLY, 0, 0);
if (!(is instanceof ifs.nsILineInputStream))
return;
var line = { value: "" };
do {
var more = is.readLine(line);// yuck, returns false for last valid line
var result = "Results of processing log " + file.fileName + " :\n";
var contents = file.getAsText("iso-8859-1");
var lines = contents.split(/[\r\n]+/);
for (var j in lines) {
var line = lines[j];
// strip off initial "-", thread id, and thread pointer; separate
// first word and rest
var matches = line.value.match(/^\-?[0-9]*\[[0-9a-f]*\]: (\S*) (.*)$/);
var matches = line.match(/^\-?[0-9]*\[[0-9a-f]*\]: (\S*) (.*)$/);
if (matches) {
var handler = matches[1];
var data = matches[2];
@ -269,7 +252,7 @@ function run() {
handlers[handler].handle_line(data);
}
}
} while (more);
}
for (var handler in handlers)
handlers[handler].dump();
@ -278,6 +261,7 @@ function run() {
result += "Summary:\n";
for (var handler in handlers)
handlers[handler].summary();
result += "\n";
var out = document.createElement("pre");
out.className = "output";
@ -285,13 +269,24 @@ function run() {
document.body.appendChild(out);
}
function run() {
var input = document.getElementById("fileinput");
var files = input.files;
for (var i = 0; i < files.length; ++i)
runfile(files[i]);
// So the user can process the same filename again (after
// overwriting the log), clear the value on the form input so we
// will always get an onchange event.
input.value = "";
}
</script>
</head>
<body>
<h1>Leak Gauge</h1>
<pre>$Id: leak-gauge.html,v 1.7 2008/02/08 19:55:03 dbaron%dbaron.org Exp $</pre>
<pre>$Id: leak-gauge.html,v 1.8 2008/02/08 19:55:34 dbaron%dbaron.org Exp $</pre>
<p>This script is designed to help testers isolate and simplify testcases
for many classes of leaks (those that involve large graphs of core
@ -315,19 +310,16 @@ to figure out under what conditions the leak occurs.</p>
<pre> setenv VAR value</pre></li>
</ul>
<p><strong>This script will not work from a Web page. It will work only
in relatively recent Mozilla-based browsers and only when loaded as a
file from your disk. You will be asked to give it permission to execute
arbitrary code. You should only grant this permission if you trust this
page.</strong></p>
<p>Once you have this log from a complete run of the browser (you have
to exit; otherwise it will look like everything leaked), you can load
this page <em>from your disk</em> (be careful not to overwrite the log
when starting the browser to load this page) and <a
href="javascript:run()">enter the filename</a> of the log. Then you'll
see the output below, which will tell you which of certain core objects
leaked and the URLs associated with those objects.</p>
this page (be careful not to overwrite the log when starting the browser
to load this page) and enter the filename of the log:</p>
<p><input type="file" id="fileinput" onchange="run()"></p>
<p>Then you'll see the output below, which will tell you which of
certain core objects leaked and the URLs associated with those
objects.</p>
</body>
</html>