interrupting --eval while(true){ ; } loops using killOp

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • None
    • Environment:
      Ubuntu 10.10, 6-core system, 16GB RAM.
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      On my fast system (and infrequently on some buildbots), it takes a long time (potentially forever) to kill while(true){} spinlocks sent to the mongod server. This seems to especially occur when using v8, seems as if the kill operation just is not able to progress. Adding a sleep(1) statement to the while() loop fixes the problem.

      While currently the problem only shows up in tests, potentially an accidentally buggy $where query may be unable to be terminated on a user's system while hogging the cpu.

              Assignee:
              Unassigned
              Reporter:
              Greg Studer (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: