Hasn't anyone noticed a memory leak on Firefox when using the
WorkerPool API ?
(Curiously I couldn't reproduce it on IE7.)
Here is a sample page to open and let run a while in Firefox. Both
cases seems to increase firefox memory usage a lot, even after
stopping the
constant reload and going to the url "about:blank" to get rid of the
context.
<html>
<head><script src='js/dojo/dojo.js'></script></head>
<body>
Some text.
<script>
var cas = parseInt(window.location.href.substr
(window.location.href.length-1));
switch (cas) {
case 1:
var wp = google.gears.factory.create('beta.workerpool');
break;
case 2:
dojo.require("evaph.cst");
var wp = google.gears.factory.create('beta.workerpool');
var idw= wp.createWorkerFromUrl( put_here_an_url );
break;
}
window.location.reload();
</script>
</body>
</html>
