<div dir="ltr">On 17 November 2014 15:27, D. Hugh Redelmeier <span dir="ltr"><<a href="mailto:hugh@mimosa.com" target="_blank">hugh@mimosa.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">| From: Clifford Ilkay <<a href="mailto:clifford_ilkay@dinamis.com">clifford_ilkay@dinamis.com</a>><br>
<span class=""><br>
| On 11/17/2014 01:27 PM, D. Hugh Redelmeier wrote:<br>
<br>
</span><span class="">| > I would like each "compartment" to be isolated and instrumented.<br>
<br>
| You just described Google Chrome.<br>
<br>
</span>That's interesting.  I originally thought so too, but others said that<br>
it didn't work out that way.  (This was years ago.)<br>
<br>
Can you really use this to figure out which tab is eating CPU?  Bonus:<br>
eating memory?<br clear="all"></blockquote><div><br></div><div>It seems like it'll provide memory consumption, but not CPU consumption.<br><br>See URL<br>    chrome://memory-redirect<br><br></div><div>I think memory consumption is more interesting than CPU consumption,<br>myself...<br></div></div></div><div class="gmail_extra">-- <br><div class="gmail_signature">When confronted by a difficult problem, solve it by reducing it to the<br>question, "How would the Lone Ranger handle this?"<br></div>
</div></div>