Thursday, 10 August, 2017 UTC


As JavaScript is getting more and more popular, teams are leveraging its support on many levels in their stack - front-end, back-end, hybrid apps, embedded devices and much more.
As shown in the GitHut stats, JavaScript is at the top in terms of Active Repositories and Total Pushes in GitHub. It doesn’t lack behind much in the other categories as well.
If projects are getting so much dependant on JavaScript, this means that developers have to be utilizing everything that the language and the ecosystem provides with deeper and deeper understanding of the internals, in order to build amazing software.
As it turns out, there are a lot of developers that are using JavaScript on a daily basis but don’t have the knowledge of what happens under the hood.


Almost everyone has already heard of the V8 Engine as a concept, and most people know that JavaScript is single-threaded or that it is using a callback queue.
In this post we’ll go through all of these concepts in detail and explain how JavaScript actually runs. By knowing those details, you’ll be able to write better, non-blocking apps that are properly leveraging the provided APIs.
If you’re relatively new to JavaScript, this blog post will help you understand why JavaScript is so “weird” compared to other languages.
And if you’re an experienced JavaScript developer, hopefully it will give you some fresh insights on how the JavaScript Runtime you’re using everyday actually works.

The JavaScript Engine

A popular example of a JavaScript Engine is Google’s V8 engine. The V8 engine is used inside Chrome and Node.js for example. Here is a very simplified view on what it looks like:
The Engine consists of two main components:
* Memory Heap — this is where the memory allocation happens
* Call Stack — this is where your stack frames are as your code executes

The Runtime

There are APIs in the browser that have been used by almost any JavaScript developer out there (e.g. “setTimeout”). Those APIs, however, are not provided by the Engine.
So, where are they coming from?
It turns out that reality is a bit more complicated.
So, we have the Engine but there is actually a lot more. We have those things called Web APIs which are extra things that browsers provide, like the DOM, AJAX, setTimeout and much more.
And then, we have the so popular event loop and the callback queue.

The Call Stack

JavaScript is a single-threaded programming language, which means it has a single Call Stack. Therefore it can do one thing at a time.
The Call Stack is a data structure which records basically where in the program we are. If we step into a function, we put it on the top of the stack. If we return from a function, we pop off the top of the stack. That’s all the stack can do.
Let’s see an example. Take a look at the following code:
function multiply(x, y) {
return x * y;
function calculateAndPrintSquare(x) {
var s = multiply(x, x);
When the engine starts executing this code, the Call Stack will be empty. Afterwards, the steps will be the following:
Each entry in the Call Stack is called a Stack Frame.
And this is exactly how stack traces are being constructed when an exception is being thrown — it is basically the state of the Call Stack when the exception happened. Take a look at the following code:
function foo() {
throw new Error('SessionStack will help you resolve crashes :)');
function bar() {
function start() {
If this is executed in Chrome (assuming that this code is in a file called foo.js), the following stack trace will be produced:
Blowing the stack” — this happens when you reach the maximum Call Stack size. And that could happen quite easily, especially if you’re using recursion without testing your code very extensively. Take a look at this sample code:
function foo() {
When the engine starts executing this code, it starts with calling the function “foo”. This function, however, is recursive and starts calling itself without any termination conditions. So at every step of the execution, the same function gets added to the Call Stack over and over again. It looks something like this:
At some point, however, the amount of function calls in the Call Stack exceeds the actual size of the Call Stack, and the browser decides to take action, by throwing an error, which can look something like this:
Running code on a single thread can be quite easy, since you don’t have to deal with complicated scenarios that are arising in multi-threaded environments — for example deadlocks.
But running on a single thread is quite limiting as well. Since JavaScript has a single Call Stack, what happens when things are slow?

Concurrency & the Event Loop

What happens when you have function calls in the Call Stack that take huge amount of time in order to be processed? For example, imagine that you want to do some complex image transformation with JavaScript in the browser.
You may ask — why is this even a problem? The problem is that while the Call Stack has functions to execute, the browser can’t actually do anything else — it’s getting blocked. This means that the browser can’t render, it can’t run any other code, it’s just stuck. And this creates problems if you want nice fluid UIs in your app.
And that’s not the only problem. Once your browser starts processing so many tasks in the Call Stack, it may stop being responsive for quite a long time. And most browsers take action by raising an error, asking you whether you want to terminate the web page.
Now, that’s not the best user experience out there, is it?
So, how can we execute heavy code without blocking the UI and making the browser unresponsive? Well, the solution is asynchronous callbacks.
This will be explained in great detail in Part 2 of the “How does JavaScript actually work” tutorial. Stay tuned :)
In the meantime, if you’re having a hard time reproducing and understanding issues in your JavaScript apps, take a look at SessionStack and get started for free.

How does JavaScript actually work: Part 1 was originally published in SessionStack Blog on Medium, where people are continuing the conversation by highlighting and responding to this story.