3.11.2: memory issues and Invalid string length

Issue workflow progress

Progress of the issue based on the Contributor Workflow

• 1. The issue provides a reproduction available on GitHub, Stackblitz or CodeSandbox

  Please make sure the graphql-eslint version under package.json matches yours.

• 2. A failing test has been provided
• 3. A local solution has been provided
• 4. A pull request is pending review

---

Describe the bug

I’m seeing some memory issues since bumping to 3.11.2.

On one repository (CI and locally):

<--- Last few GCs --->

[107:0x6a93a00]    37386 ms: Scavenge 2026.1 (2076.3) -> 2021.6 (2077.6) MB, 8.5 / 0.0 ms  (average mu = 0.750, current mu = 0.568) allocation failure; 
[107:0x6a93a00]    37415 ms: Scavenge 2027.4 (2077.9) -> 2023.7 (2079.9) MB, 8.7 / 0.0 ms  (average mu = 0.750, current mu = 0.568) allocation failure; 
[107:0x6a93a00]    37891 ms: Scavenge 2029.5 (2079.9) -> 2025.3 (2097.2) MB, 459.1 / 0.0 ms  (average mu = 0.750, current mu = 0.568) allocation failure; 


<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 0xb6dd40 node::Abort() [node]
 2: 0xa7db1c  [node]
 3: 0xd47560 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xd47907 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xf24cc5  [node]
 6: 0xf371ad v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 7: 0xf118ae v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 8: 0xf12c77 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 9: 0xef3e4a v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
10: 0x12b73ef v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
11: 0x16e9039  [node]
Aborted (core dumped)

Exited with code exit status 134

on another, the CI simply kills it after a short while (locally:

Killed

Exited with code exit status 137

Locally I’m seeing this:

Oops! Something went wrong! :(

ESLint: 8.24.0

RangeError: Cannot read config file: /Users/userName/repo/.eslintrc.js
Error: Invalid string length
    at updateOutput (/Users/userName/repo/node_modules/ts-node/src/index.ts:1666:66)
    at Object.compile (/Users/userName/repo/node_modules/ts-node/src/index.ts:1460:20)
    at Module.m._compile (/Users/userName/repo/node_modules/ts-node/src/index.ts:1617:30)
    at Module.m._compile (/Users/userName/repo/node_modules/ts-node/src/index.ts:1618:23)
    at Module.m._compile (/Users/userName/repo/node_modules/ts-node/src/index.ts:1618:23)
    at Module.m._compile (/Users/userName/repo/node_modules/ts-node/src/index.ts:1618:23)
    at Module.m._compile (/Users/userName/repo/node_modules/ts-node/src/index.ts:1618:23)
    at Module.m._compile (/Users/userName/repo/node_modules/ts-node/src/index.ts:1618:23)
    at Module.m._compile (/Users/userName/repo/node_modules/ts-node/src/index.ts:1618:23)
    at Module.m._compile (/Users/userName/repo/node_modules/ts-node/src/index.ts:1618:23)
[...]

To Reproduce Steps to reproduce the behavior:

Expected behavior

Environment:

• OS: MacOS 12.6
• @graphql-eslint/eslint-plugin: 3.11.2
• Node.js: 18.9.1

Additional context

[B2o5T]

should be fixed in @graphql-eslint/eslint-plugin@3.12.0

[B2o5T]

@jlowcs thank you! 🎉🚀