Chrom Debugger Crashes

Chrom Debugger Crashes

Dear JQuery Folks,

i have write a piece of code which you can see in here:

  2. ///////////////////////////////
  3. //   Handle Multiple Views   //
  4. ///////////////////////////////

  6. function setActiveView(multiViewId, viewId) {
  7.     if (multiViewId == undefined) throw "multiViewId is Undifined";
  8.     if (viewId == undefined) throw "viewId is Undifined";

  10.     var mv = $(".multi-view").filter(function () {
  11.         if ($(this).data("multiViewId") == undefined) throw "data-multi-view-id is not defined over multi-view";
  12.         return $(this).data("multiViewId") === multiViewId;
  13.     });
  14.     var views = mv.find(".single-view").filter(function () {
  15.         if ($(this).hasClass("single-view"))
  16.             if ($(this).parent().hasClass("multi-view") && $(this).parent().data("multiViewId") === multiViewId)
  17.                 return true;

  19.         return false;
  20.     });
  21.     views.attr("class", "single-view view-hide");
  22.     var newActivatedView = views.filter(function () {
  23.         if ($(this).data("viewId") == undefined) throw "data-view-id is not defined over single-view";
  24.         return $(this).data("viewId") === viewId;
  25.     });

  27.     newActivatedView.removeClass("view-hide");
  28.     newActivatedView.addClass("view-show");
  29. }
it normally work well, but if i put a break in line 15 and start tracing as i needed 5 minutes ago, once it reach the following part, the debugger crashes...

  1.                 // Go through the array, only saving the items
  2. // that pass the validator function
  3. for ( ; i < length; i++ ) {
  4. retVal = !!callback( elems[ i ], i );
  5. if ( inv !== retVal ) {
  6. ret.push( elems[ i ] );
  7. }
  8. }
it stay where it is, and CPU load shows it's processing something. i'm not sure why something causing it, but for sure it's matter of asynchronous functionality, which may cause this even happen on a compute with faster or slower CPU, well, how to bypass it,.... is it dangerous for me to go through this? 
the debugger, never leave the function and stay where it is.

before i write this thread, i restart my chrome, end tasking it on windows, and before submit this thread, i again test the issue, it didn't fall for the same thing,... but i still need to be worry, so i post this. it my be caused by my own chrome loading badly, or may be ... BTW, the code didn't change.