Skip to content

Angular SSR can crash AngularAppEngine servers with a single aborted request (22.2.6 regression) #34754

Open

Description

@SkyZeroZx

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

22.2.5

Description

Since @angular/ssr 22.2.6, a client that disconnects while a page is still rendering can kill the server process when it runs on AngularAppEngine: plain node:http, Hono, H3, srvx, Deno or Bun. The Express server from ng new --ssr is fine, because AngularNodeAppEngine installs process-wide error handlers.

#34568 made renderAngular() destroy the platform when request.signal aborts:

const abortHandler = () => void destroy();
try {
signal?.addEventListener('abort', abortHandler, { once: true });

The host still gets the usual AbortError and handles it. What kills the process is the work that was still running. The clearest case is an app initializer: once it settles, bootstrap() reads the destroyed injector, and the internal error handler rethrows the NG0205 from a setTimeout because the injector is destroyed. Neither the app nor the host's try/catch can catch that, so it doesn't matter how the initializer is written:

Pending when the client disconnects, on AngularAppEngine Process
provideAppInitializer from its usage notes exit 1
the same wrapped in try/catch exit 1
an initializer that only waits on a 100 ms timer exit 1
PendingTasks.run() as the zoneless guide shows it, awaiting an HttpClient call exit 1
firstValueFrom(http.get(...)) in async ngOnInit() (zoneless) exit 1
subscribe(), resolvers, guards, httpResource, resource() alive
the try/catch initializer on 22.2.5, or on AngularNodeAppEngine alive

The ngOnInit row is the other path: FetchBackend completes without a value once the app is destroyed, so firstValueFrom() rejects with EmptyError and nobody holds that promise. PendingTasks.run() passes that error to the same internal error handler, so it's rethrown from a setTimeout too.

It doesn't take precise timing. Every abort that arrived while the server was waiting on its backend killed it, 310 out of 310 with backends from 1 ms to 1 s, and nginx with its default config passes the abort on. The other pages that were rendering go down too. With Docker's restart: always, one aborted request every two seconds left the site serving 312 pages a minute instead of 5,584.

#34568 is right to stop the render, but the platform shouldn't be destroyed while that work is still pending, so the abort stays inside the promise handle() returns, the way it did on 22.2.5. AngularAppEngine is meant for platforms other than Node.js, so it can't count on process.on() handlers like AngularNodeAppEngine does.

Minimal Reproduction

https://github.com/SkyZeroZx/angular-ssr-abort-crash-lab

ng new --ssr with provideHttpClient(), RenderMode.Server on **, the SSR guide's non-Node entry on node:http, and a component that waits for its data during the render (api.mjs answers in 100 ms):

async ngOnInit() {
  const { name } = await firstValueFrom(
    this.http.get<{ name: string }>('http://127.0.0.1:4400/profile'),
  );
  this.profile.set(name);
}
npm ci && npx ng build
node api.mjs &
node dist/aborted-render-process/server/server.mjs &
sleep 2
curl -sS -o /dev/null -w "%{http_code}\n" http://localhost:4000/
curl -sS -m 0.05 http://localhost:4000/
sleep 1
curl -sS http://localhost:4000/
200
curl: (28) Operation timed out after 55 milliseconds with 0 bytes received
curl: (7) Failed to connect to localhost:4000 after 0 ms: Could not connect to server

The initializer version is in variants/initializer-trycatch, and cd docker && sh variants.sh initializer-trycatch builds and runs it. The README has the rest.

Exception or Error

The try/catch initializer, development build:

dist/aborted-render-process/server/main.server.mjs:4818
            throw e;
            ^

RuntimeError: NG0205: Injector has already been destroyed. Find more at https://v22.angular.dev/errors/NG0205
    at assertNotDestroyed (dist/aborted-render-process/server/main.server.mjs:3546:11)
    at R3Injector.get (dist/aborted-render-process/server/main.server.mjs:3303:5)
    at dist/aborted-render-process/server/main.server.mjs:26095:38
    at async renderAngular (dist/aborted-render-process/server/main.server.mjs:43273:24)


The ngOnInit repro, development build:

node:internal/process/promises:394
    triggerUncaughtException(err, true /* fromPromise */);
    ^
Error
    at new EmptyErrorImpl (dist/aborted-render-process/server/main.server.mjs:1783:3)
    at Object.complete (dist/aborted-render-process/server/main.server.mjs:1802:18) {
  message: 'no elements in sequence'
}

Your Environment

@angular/ssr      22.2.7
@angular/core     22.2.6, also 22.3.0
Node.js           24.16.0 on Windows 11, 24.22.3 in Docker
Also tried        Hono 4.13, H3 2.0, srvx 1.0, Deno 2.9.8, Bun 1.4.4, nginx 1.30

Anything else relevant?

I think this is a vulnerability according to the SECURITY.md, which says:

DoS attacks which waste server resources significantly beyond the cost of the attacker's request may be security issues.

Here a single request crashes the server.

Activity

  1. added this to the needsTriage milestone on Nov 19, 2026
  2. added a commit that references this issue on Nov 19, 2026
    106adcc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions