prisma: Engine freezes all requests/responses in 2.0.0-beta.2

Bug description

Beta.2 freezes all requests to the application. The queries never resolve, and the requests never return any data.

I tested in NextJS, although even loading prisma with beta.2 outside the NextJS app (using just node) it still hangs.

Removing the query/request code from NextJS sees it start resolving requests as normal.

How to reproduce

Reproduction:

https://github.com/asciant/prisma-next-db-slots/tree/testing-beta-2 Note: this is a separate branch of a 2.0.0-beta.1 issue #1438 (https://github.com/prisma/prisma/issues/1438#issuecomment-610196306)

1. Clone the repository (https://github.com/asciant/prisma-next-db-slots);
2. Switch to the testing-beta-2 branch
3. Have your own local Postgres server running, and setup the DATABASE_URL connection string environment variable;
4. Install the dependencies (npm install), generate the prisma client (npx prisma generate) and run the migration (npx prisma migrate up --experimental);
5. Start the server (npm run dev) and visit the page in the browser (http://localhost:3000).

Expected behavior

The prisma engine to respond with the results of the query.

Prisma information

Included in the reproduction.

Environment & setup

• OS: MacOS
• Database: PostgreSQL 12.2
• Prisma version:

Environment variables loaded from ./prisma/.env
@prisma/cli          : 2.0.0-beta.2
Current platform     : darwin
Query Engine         : query-engine 76857c35ba1e1764dd5473656ecbbb2f739e1822 (at /usr/local/lib/node_modules/@prisma/cli/query-engine-darwin)
Migration Engine     : migration-engine-cli 76857c35ba1e1764dd5473656ecbbb2f739e1822 (at /usr/local/lib/node_modules/@prisma/cli/migration-engine-darwin)
Introspection Engine : introspection-core 76857c35ba1e1764dd5473656ecbbb2f739e1822 (at /usr/local/lib/node_modules/@prisma/cli/introspection-engine-darwin)

• Node.js version: v13.12.0