When graphqlgen large schema will get stuck

[Victorkangsh]

Description

In one of my projects, the datamodel has five hundred lines. My schema.graphql file imports the generated prisma.graphql schema file and has a hundred lines of Query and Mutation.

I get stuck when I run graphqlgen. Cpu and memory are slightly higher. I noticed a prompt for the find prettier, but I still didn't succeed after removing the prettier configuration.

My three computers have linux, mac, and windows systems, and they are not working properly. But the surprise is that my mac has been successful once, just once.

Steps to reproduce

When schema.graphql too large.

My other small project run graphqlgen perfectly.

Expected results

Graphqlgen work success.

Actual results

Stucked. And console has no message.

Versions

• graphqlgen: 0.4.0
• OS name and version: mac: 16G memory, mojava(darwin-x64). windows: win10 16G memory i7.
• Node: node-v10.8.0

[Victorkangsh]

Supplement：
When wait 1 hour later, console log err as follows：

graphqlgen
<--- Last few GCs --->

[14832:000002002A721AF0]  8948164 ms: Mark-sweep 1159.4 (1202.0) -> 1159.4 (1165.5) MB, 3679.4 / 0.0 ms  last resort GC in old space requested
[14832:000002002A721AF0]  8948951 ms: Mark-sweep 1159.4 (1165.5) -> 1159.4 (1165.5) MB, 786.8 / 0.0 ms  last resort GC in old space requested


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0000038B35425EE1 <JSObject>
    0: builtin exit frame: concat(this=000002C19A6AE511 <JSArray[40009211]>,000002C19A682201 <JSArray[18728217]>)

    1: flatten(aka flatten) [C:\Users\T47\AppData\Roaming\npm\node_modules\graphqlgen\dist\utils.js:~49] [pc=000002BC79E8D883](this=0000006577382311 <undefined>,a=000002C19A6AE511 <JSArray[40009211]>,b=000002C19A682201 <JSArray[18728217]>)
    2: arguments adaptor frame: 4->2
    ...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

And when I set --max_old_space_size setting it still not working.

[LawJolla]

Same issue. Looks like it's in a loop of some kind. I am importing one type from Prisma via graphql-import.

MacOS 10.14.1, 2015 iMac with 16gb RAM and 2016 MBP with 8gb RAM

<--- Last few GCs --->

[1153:0x104001c00]   403737 ms: Mark-sweep 1219.6 (1227.3) -> 1219.6 (1226.3) MB, 736.6 / 0.0 ms  (average mu = 0.079, current mu = 0.000) allocation failure GC in old space requested
[1153:0x104001c00]   404472 ms: Mark-sweep 1219.6 (1226.3) -> 1219.6 (1225.3) MB, 735.3 / 0.0 ms  (average mu = 0.052, current mu = 0.000) last resort GC in old space requested


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x05326251d9f1 <JSObject>
    0: builtin exit frame: concat(this=0x0532c9e86071 <JSArray[15602824]>,0x0532e3b266a1 <JSArray[14814181]>,0x0532c9e86071 <JSArray[15602824]>)

    1: /* anonymous */(aka /* anonymous */) [0x53221beec69] [/Users/dennismacbookpro/WebstormProjects/wk-mono-repo/node_modules/graphqlgen/dist/generators/common.js:~142] [pc=0x19d5dd850c51](this=0x0532387825b1 <undefined>,0x05328ef92ef9 <String[15]: S...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x10005eeab node::Abort() [/usr/local/bin/node]
 2: 0x10005f68a node::FatalTryCatch::~FatalTryCatch() [/usr/local/bin/node]
 3: 0x100172027 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
 4: 0x100171fc8 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
 5: 0x100433768 v8::internal::Heap::UpdateSurvivalStatistics(int) [/usr/local/bin/node]
 6: 0x100435185 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [/usr/local/bin/node]
 7: 0x100432afd v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/usr/local/bin/node]
 8: 0x1004318f3 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/bin/node]
 9: 0x100431b8f v8::internal::Heap::CollectAllAvailableGarbage(v8::internal::GarbageCollectionReason) [/usr/local/bin/node]
10: 0x100439835 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/usr/local/bin/node]
11: 0x1004195b3 v8::internal::Factory::AllocateRawArray(int, v8::internal::PretenureFlag) [/usr/local/bin/node]
12: 0x100419469 v8::internal::Factory::NewFixedArrayWithFiller(v8::internal::Heap::RootListIndex, int, v8::internal::Object*, v8::internal::PretenureFlag) [/usr/local/bin/node]
13: 0x100424f5a v8::internal::Factory::NewJSArrayStorage(v8::internal::Handle<v8::internal::JSArray>, int, int, v8::internal::ArrayStorageAllocationMode) [/usr/local/bin/node]
14: 0x100424e2b v8::internal::Factory::NewJSArray(v8::internal::ElementsKind, int, int, v8::internal::ArrayStorageAllocationMode, v8::internal::PretenureFlag) [/usr/local/bin/node]
15: 0x1003ce3ee v8::internal::ElementsAccessor::Concat(v8::internal::Isolate*, v8::internal::Arguments*, unsigned int, unsigned int) [/usr/local/bin/node]
16: 0x1001d9220 v8::internal::(anonymous namespace)::Fast_ArrayConcat(v8::internal::Isolate*, v8::internal::BuiltinArguments*) [/usr/local/bin/node]
17: 0x1001d6d5a v8::internal::Builtin_Impl_ArrayConcat(v8::internal::BuiltinArguments, v8::internal::Isolate*) [/usr/local/bin/node]
18: 0x19d5dd7cfcdd 
19: 0x19d5dd850c51 
20: 0x19d5dd7876a6 
21: 0x19d5dd871a16 
[1]    1153 abort      graphqlgen

[rowlandekemezie]

@Victorkangsh Did you try downgrading to 0.3.0. Mine got stuck without any info tho' but works fine with 0.3.0

[LawJolla]

@mentrie Thanks for the suggestion. But if I downgrade, then I'm hit with the #280 bug 😢

[rowlandekemezie]

@LawJolla Right. For the past 1hr, 0.4.0 is still running 😢

[frankdugan3]

Same issue here. Can't use at all until this is resolved. My system has 32 GB of RAM, and it still doesn't work. Haven't let it run for an hour, but after several minutes I still have plenty of RAM left.

[woss]

I've spend few hours debugging the package and it seems that here :
https://github.com/prisma/graphqlgen/blob/03336f01d1257643c4b24577a397df44bd00076a/packages/graphqlgen/src/generators/common.ts#L228 it turns into the endless loop.

When i add Mutation to my schema with the same name as one in the prisma.graphql it runs until it fails.

[woss]

@mentrie Thanks for the suggestion. But if I downgrade, then I'm hit with the #280 bug 😢

that has been fixed. I've downgraded to 0.3.0 and it worked even with the schema that fails on 0.4.0

[LawJolla]

@mentrie Thanks for the suggestion. But if I downgrade, then I'm hit with the #280 bug 😢

that has been fixed. I've downgraded to 0.3.0 and it worked even with the schema that fails on 0.4.0

@woss It's still an issue for me in 0.3.0. This project looked promising, but it now appears under maintained if not abandoned. I've given up and gone back to Javascript to actually get things built... pesky deadlines. :)

[jasonkuhrt]

Anyone have a schema that leads to this issue that they can share?

[Victorkangsh]

@jasonkuhrt I have figured out its problem, it has nothing to do with the size of the schema, but an error when using the imported Input Type.
like this example : https://github.com/prisma/graphql-prisma-typescript/blob/master/src/schema.graphql

when you add some Mutation using imported Input Type it will stuck:

# import * from "./generated/prisma.graphql"
type Mutation {
  addPaymentMethod(
    data: PaymentCreateInput
  ): MutationResult!
  book(
    data: BookingCreateInput
  ): MutationResult!
}

[vdiaz1130]

This bug renders graphqlgen unusable for me. Running with version 3 I get a bunch of TS errors while running on latest gets stuck.

I was more specific with my imports from Prisma generated code.

// I used
# import Post, User, UserCreateInput, UserUpdateInput from './generated/prisma.graphql'

// VS
# import * from "./generated/prisma.graphql"

node -v
v11.4.0

npm -v
6.4.1

OSx 10.12.6

prisma -v
prisma/1.22.2

https://ibb.co/0DjYqkG

Any hacky workaround ideas for now? A nightly I can test?