title: Using Firebug with Knockout causes "unresponsive script error"
body: <p>I'm building a screen with Knockout using Firefox with Firebug open on the page. </p>
  
  <p>In a very specific case I get an unresponsive script error from Firefox and after much testing I've narrowed it down to only happen in this specific case when Firebug is open. When it is closed I don't get the error.</p>
  
  <p>After stepping through the Knockout debug js a number of times with this error I've found that the first "unresponsive script" popup occurs near the processing of end comment (1807)</p>
  
  <pre><code>setDomNodeChildren: function(node, childNodes) {
                          if (!isStartComment(node))
                              ko.utils.setDomNodeChildren(node, childNodes);
                          else {
                              ko.virtualElements.emptyNode(node);
                              var endCommentNode = node.nextSibling; // Must be the next sibling, as we just emptied the children
                              for (var i = 0, j = childNodes.length; i &lt; j; i++)
                                  endCommentNode.parentNode.insertBefore(childNodes[i], endCommentNode);
                          }
                      },
  </code></pre>
  
  <p>or near 1728 which is also near work about the end comment</p>
  
  <pre><code>function isEndComment(node) {
                      return (node.nodeType == 8) &amp;&amp; (commentNodesHaveTextProperty ? node.text : node.nodeValue).match(endCommentRegex);
                  }
  </code></pre>
  
  <p>but it's in a different location each time and if I click 'continue' on the unresponsive script popup I can just keep going.</p>
  
  <p>Running without Firebug gives no error and running in Chrome with or without developer tools gives no error.</p>
  
  <p>I'm at a loss as to what to try or what code to post to help resolve my problem as I've made many screens with Knockout using Firefox and Firebug and this is the first time I've run into a problem like this. </p>
  
  <p>But I would very much appreciate any hints or advice as to how to get firebug to stop causing this problem. (Although maybe I'll just have to move to Chrome...)</p>