<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<blockquote cite="mid:20130104201748.GJ16474@pde.eff.org"
type="cite">
<pre wrap=""><font color="#3333ff" face="sans-serif"><i>It's a threshhold value. Setting it lower gives you "deeper" logs :)</i></font></pre>
</blockquote>
<br>
Ah. OK. Not what I would have expected, but I understand now.<br>
<br>
<blockquote cite="mid:20130104201748.GJ16474@pde.eff.org"
type="cite">
<pre wrap=""><font color="#3333ff" face="sans-serif"><i>It's possible that we're either looking at an incompatibility issue causing a memory leak, or simply a memory leak in one of these other extensions plus an unrelated, less-serious bug causing the error message. Let's see how we go with the verbose logs before trying to play the bisection game with all of those extensions.</i></font></pre>
</blockquote>
<br>
I'm going to try running for a few days with HTTPS-Everywhere
disabled (!!) and see if Firefox still crashes.<br>
<br>
<blockquote cite="mid:20130104201748.GJ16474@pde.eff.org"
type="cite">
<pre wrap=""><font color="#3333ff" face="sans-serif"><i>Opens the profile manager, so that you can create an alternative profile to run in parallel with your regular one.</i></font>
</pre>
</blockquote>
<br>
Since (as I said) I recently switched to a brand-new profile (and
continued to get crashes), I assume nothing would be gained by doing
this again, right?<br>
<br>
Rich Wales (<a class="moz-txt-link-abbreviated" href="mailto:richw@richw.org">richw@richw.org</a>)<br>
Palo Alto, California, USA<br>
</body>
</html>