A job queue in two lines of JavaScript(jameshfisher.com)
jameshfisher.com
A job queue in two lines of JavaScript
https://jameshfisher.com/2025/07/07/a-job-queue-in-two-lines-of-js/
39 comments
The chain variable continuously grows because each call to enqueue() creates a new promise that references the previous one. This creates an ever-growing chain of promises that never gets garbage collected.
Though it seems like that, no.
(If the runtime maintains async stack traces, that could be an issue...but that is a common issue, and the stack depth is limited.)
a = b.then(c);
(If the runtime maintains async stack traces, that could be an issue...but that is a common issue, and the stack depth is limited.)
That's not how promises work, there's no chain. It's no different from
await job1()
await job2()
await job3()
await job4()
Couldn’t the browser garbage collect the promises (and their callbacks) that have been rejected or resolved? I.e. effectively “shift” the promises at the start of the queue that have been dealt with and will never be relevant again?
At least this stackoverflow answer suggests the handlers are GC’ed: https://stackoverflow.com/questions/79448475/are-promise-han...
At least this stackoverflow answer suggests the handlers are GC’ed: https://stackoverflow.com/questions/79448475/are-promise-han...
At least in V8, this is not the case. To prove it, start a Chromium-based browser with the command-line flag --js-flags=--expose-gc, then go to https://runjs.app/play/#aWYgKCF3aW5kb3cuZ2MpIHsKICB0aHJvdyBu...
Why does the promise returned by a promise’s then() method need to reference that promise?
The original promise needs to reference the chained promise, not the other way round.
As jobs complete I would expect the top of the chain to be eligible to be garbage collected.
The original promise needs to reference the chained promise, not the other way round.
As jobs complete I would expect the top of the chain to be eligible to be garbage collected.
> This creates an ever-growing chain of promises that never gets garbage collected.
Modern frontend development performance best practise is to allow for garbage collection only when the browser crashes.
Modern frontend development performance best practise is to allow for garbage collection only when the browser crashes.
I wonder if people who are claiming its not the case ever tried to use promises in hardcore ways like this, chaining 10s of thousands of calls. You often hit some bullshit, i.e. Promise.race is a big cause of issues.
Even if you are doing `then().then()`, something _else_ in the code base could retain the promise somehow and then your whole chain isn't GCable!
For example https://github.com/rxaviers/async-pool library that implements concurrency for async iterators (and uses promise.race) subtly creates GC pressure which you dont see until you make a whole lot of calls and suddenly its slow
Even if you are doing `then().then()`, something _else_ in the code base could retain the promise somehow and then your whole chain isn't GCable!
For example https://github.com/rxaviers/async-pool library that implements concurrency for async iterators (and uses promise.race) subtly creates GC pressure which you dont see until you make a whole lot of calls and suddenly its slow
[deleted]
Nope.
I came across this trick a few months ago when I was dealing with what seemed to be a race condition from a chrome-only API, and I just felt so clever! I don't remember though whether the race condition actually was one or not though, and I eventually had to rip that entire class out of my codebase. But it's such a good feeling to know I came up with a solution that clever all by myself.
Chaining promises like this is not a good idea for high throughput cases (creates gc pressure), but perfectly valid for regular cases.
Huh?
It creates 1 object allocation per enqueue.
It creates 1 object allocation per enqueue.
yeah but it creates closure as well, which typically references some objects that isn't easy to GC. So if you have long-living promise with some data captured in closure, it will not be cleared. So doing then().then().then() may not release objects referenced in callbacks that resolved time ago.
There are zero closures here.
To make it slightly more idiomatic, you can use chain.finally(job) instead of chain.then(job, job). (All browsers have supported this API for over seven years.)
If you wanted to e.g. log something on failures, you’d need to do something like this:
chain
.then(job)
.catch((err) => {
console.error(err);
return job();
});
> If you need a job queue in JS
type Job = () => Promise<unknown>;
It's trivial to remove the type annotations.
A production grade application would need a much more robust mechanism like BullMQ
There are use cases for a non-persistent task queue, like doing things one at a time on the frontend. (JavaScript is single-threaded but will interleave multiple separate async call chains that each span multiple event-loop iterations, and there could be situations where you might not want that.)
Anybody willing to walk me through this code? I don't get it.
chain is a global variable. It starts with an empty promise. First call to enqueue changes the (global)value of chain to emptyPromise.then(firstJob), second call to enqueue changes it to emptyPromise.then(firstJob).then(secondJob) and so on.
JavaScript promises are objects with a resolver function and an internal asynchronous computation. At some point in the future, the asynchronous computation will complete, and at that point the promise will call its resolver function with the return value of the computation.
`prom.then(fn)` creates a new promise. The new promise’s resolver function is the `fn` inside `then(fn)`, and the new promise’s asynchronous computation is the original promise’s resolver function.
`prom.then(fn)` creates a new promise. The new promise’s resolver function is the `fn` inside `then(fn)`, and the new promise’s asynchronous computation is the original promise’s resolver function.
That's TS, not JS.
One line of TS, then two lines of JS (with a type annotation in one of them)
It’s not even 2 lines:
1. Type definition 2. Chain definition 3. Enqueue definition
1. Type definition 2. Chain definition 3. Enqueue definition
Line 1 is fully erased when transpiling, leaving two lines of JavaScript.
But you still had to write it and it's required to get the result, so I don't see any rational for not counting it.
Transpilation does not change the fact that the input is these 3 lines of code in 2 different languages.
Transpilation does not change the fact that the input is these 3 lines of code in 2 different languages.
Right, and only two of those lines are JavaScript. The type definition is not required to get the result.
I noticed the same thing when I saw the code. Is it honest for TFA to title it as "2-lines of Javascript" in this case?
I came here to make the same comment.
I wonder why are you downvoted for being as factual and neutral as it is technically possible.
I wonder why are you downvoted for being as factual and neutral as it is technically possible.
I think because a reader who doesn't want to use TypeScript can trivially remove the type annotations, so they're not actually a barrier to using this code in JavaScript. Some people might also be suspicious that the reason to bring this up is to imply hostility to JavaScript tooling that requires a build step, since it's become popular to hate on this.
So as a community of developers we're totally okay calling TypeScript "JavaScript" because ... mentioning that hard cold fact is a sign of hostility towards TS? Ok. Got it.
Oh, come on.