In Javascript, is it expensive to use try-catch blocks even if an exception is never thrown?

by

Are you doing typical CRUD UI code? Use try catches, use loops that go to 10000 for no reason sprinkled in your code, hell, use angular/ember – you will not notice any performance issue.

If you are doing low level library, physics simulations, games, server-side etc then the never throwing try-catch block wouldn’t normally matter at all but the problem is that V8 didn’t support it in their optimizing compiler until version 6 of the engine, so the entire containing function that syntactically contains a try catch will not be optimized. You can easily work around this though, by creating a helper function like tryCatch:

function tryCatch(fun) {
    try {
        return fun();
    }
    catch(e) {
        tryCatch.errorObj.e = e;
        return tryCatch.errorObj;
    }
}
tryCatch.errorObj = {e: null};


var result = tryCatch(someFunctionThatCouldThrow);
if(result === tryCatch.errorObj) {
    //The function threw
    var e = result.e;
}
else {
    //result is the returned value
}

After V8 version 6 (shipped with Node 8.3 and latest Chrome), the performance of code inside try-catch is the same as that of normal code.

More Related Contents:

  1. Defining methods via prototype vs using this in the constructor – really a performance difference?
  2. What’s the best way to convert a number to a string in JavaScript?
  3. When does reflow happen in a DOM environment?
  4. Controlling fps with requestAnimationFrame?
  5. JavaScript variables declare outside or inside loop?
  6. regex.test V.S. string.match to know if a string matches a regular expression
  7. Should Github be used as a CDN for javascript libraries? [closed]
  8. How to avoid freezing the browser when doing long-running computations in Javascript
  9. Why is bind slower than a closure?
  10. JavaScript Exception Handling
  11. Is it possible to catch exceptions thrown in a JavaScript async callback?
  12. alias to chrome console.log
  13. try..catch not catching async/await errors
  14. Knockout.js incredibly slow under semi-large datasets
  15. v8 JavaScript performance implications of const, let, and var?
  16. Object.keys() complexity?
  17. Why is `.catch(err => console.error(err))` discouraged?
  18. JavaScript performance difference between double equals (==) and triple equals (===)
  19. Node.js catch ENOMEM error thrown after spawn
  20. Best way to execute js only on specific page
  21. Why Array.forEach is slower than for() loop in Javascript? [duplicate]
  22. Does the tag position in HTML affects performance of the webpage?
  23. setTimeout() with string or (anonymous) function reference? speedwise [closed]
  24. Why does a return in `finally` override `try`?
  25. Javascript (jQuery) performance measurement and best practices (not load time)
  26. Javascript – insert an array inside another array
  27. Extending String.prototype performance shows that function calls are 10x faster
  28. Why is try {} .. catch() not working with async/await function?
  29. Does using a document fragment really improve performance?
  30. value of using React.forwardRef vs custom ref prop

Leave a Comment