Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SQL Server: `prisma generate` fails with error "memory allocation of [86GB] failed"

See original GitHub issue

Bug description

We just upgraded from Prisma 2.30.2 to 3.6.0.

Running prisma generate fails with this error message (after a very long time, 30mins plus!):

$ npx prisma generate
Prisma schema loaded from prisma\schema.prisma
memory allocation of 42949672960 bytes failed

The same problem occurs with Prisma 3.0.2

How to reproduce

I created a small repo with our schema that reproduces the issue: https://github.com/peteralbert/prisma-generate-issue

Expected behavior

Command should generate Prisma client without request 86GB of RAM

Prisma information

See schema in the repo

Environment & setup

OS: Windows Server 2019 Standard
Database: SQL Server
Node.js version: v14.15.1

Prisma Version

prisma                  : 3.6.0
@prisma/client          : 3.6.0
Current platform        : windows
Query Engine (Node-API) : libquery-engine dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at ..\..\node_modules\@prisma\engines\query_engine-windows.dll.node)
Migration Engine        : migration-engine-cli dc520b92b1ebb2d28dc3161f9f82e875bd35d727
(at ..\..\node_modules\@prisma\engines\migration-engine-windows.exe)
Introspection Engine    : introspection-core dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at ..\..\node_modules\@prisma\engines\introspection-engine-windows.exe)
Format Binary           : prisma-fmt dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at ..\..\node_modules\@prisma\engines\prisma-fmt-windows.exe)
Default Engines Hash    : dc520b92b1ebb2d28dc3161f9f82e875bd35d727
Studio                  : 0.440.0

Issue Analytics

State:
Created 2 years ago
Comments:15 (8 by maintainers)

Top GitHub Comments

2reactions

pantharshit00commented, Dec 8, 2021

Thanks for reporting. I can reproduce this.

1reaction

peteralbertcommented, Dec 23, 2021

awesome! will verify after xmas break

Top Results From Across the Web

Resolve Out Of Memory Issues - SQL Server - Microsoft Learn

Resolve page allocation failures due to insufficient memory when sufficient memory is available. If you get the error message, Disallowing page ...

Prisma 3.7.0 Release - GitClear

fix(sdk): avoid unlinking QE library when running "prisma generate" ... SQL Server: prisma generate fails with error "memory allocation of [86GB] failed" ...

Memory Allocation Failure Question - SQLServerCentral

"The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected...

Untitled

Jeroen dielemans galder, D'integrazione, Linx 10 light review, Wrong way driving ... Stadtwald krefeld spiel ohne ranzen, Funny gamers fail, Hotel isola del ......

keying qpsk transmission: Topics by Science.gov

Quadrature phase-shift keying (QPSK) is usually generated using an ... by 10 dB while obtaining a 5000 hr 'mean time between failure'.