[@opentelemetry/instrumentation-fetch] Memory leak in NextJS app

[cpatti97100]

What happened?

Steps to Reproduce

NodeJS 18 (but also 20)
NextJS 13

Stress test by having Node perform a significant number of outgoing requests using fetch

Expected Result

App memory usage remains almost constant in time, like it was before introducing @opentelemetry/instrumentation-fetch

Actual Result

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

this started to happen after introducing @opentelemetry/instrumentation-fetch

Additional Details

Related work:
#4063
#3413
#4333
#4393

Now that I think of it, can these 3 packages be active together?

const { FetchInstrumentation } = require('@opentelemetry/instrumentation-fetch')
const { HttpInstrumentation } = require('@opentelemetry/instrumentation-http')
const { NetInstrumentation } = require('@opentelemetry/instrumentation-net')

OpenTelemetry Setup Code

instrumentation.node.js

const process = require('process')
const { Resource } = require('@opentelemetry/resources')
const { NodeSDK } = require('@opentelemetry/sdk-node')
const { DnsInstrumentation } = require('@opentelemetry/instrumentation-dns')
const { FetchInstrumentation } = require('@opentelemetry/instrumentation-fetch')
const { HttpInstrumentation } = require('@opentelemetry/instrumentation-http')
const { NetInstrumentation } = require('@opentelemetry/instrumentation-net')
const { PinoInstrumentation } = require('@opentelemetry/instrumentation-pino')
const { OTLPTraceExporter } = require('@opentelemetry/exporter-trace-otlp-grpc')

function initTelemetry(endpoint) {
  const sdk = new NodeSDK({
    instrumentations: [
      new DnsInstrumentation(),
      new FetchInstrumentation(),
      new HttpInstrumentation(),
      new NetInstrumentation(),
      new PinoInstrumentation(),
    ],
    resource: new Resource({
      'service.cluster': process.env.PROGRAM,
      'service.environment': process.env.ENVIRONMENT,
      'service.module': process.env.MODULE,
      'service.name': process.env.APP_NAME,
      'service.product': process.env.PRODUCT,
      'service.team': process.env.TEAM,
      'service.tenant': process.env.TENANT,
      'service.version': process.env.VERSION,
    }),
    traceExporter: new OTLPTraceExporter({
      url: endpoint,
    }),
  })

  sdk.start()

  process.on('SIGTERM', () => {
    sdk
      .shutdown()
      .then(() => console.log('Tracing terminated'))
      .catch((error) => console.log('Error terminating tracing', error))
      .finally(() => process.exit(0))
  })
}

if (process.env.OTEL_EXPORTER_OTLP_ENDPOINT) {
  initTelemetry(process.env.OTEL_EXPORTER_OTLP_ENDPOINT)
}

package.json

{ "dependencies": {
    "@opentelemetry/api": "^1.7.0",
    "@opentelemetry/exporter-trace-otlp-grpc": "^0.46.0",
    "@opentelemetry/instrumentation-dns": "^0.32.5",
    "@opentelemetry/instrumentation-fetch": "^0.46.0",
    "@opentelemetry/instrumentation-http": "^0.46.0",
    "@opentelemetry/instrumentation-net": "^0.32.5",
    "@opentelemetry/instrumentation-pino": "^0.34.5",
    "@opentelemetry/resources": "^1.19.0",
    "@opentelemetry/sdk-node": "^0.46.0",
}}

Relevant log output

No response

[pichlermarc]

@cpatti97100 @opentelemetry/instrumentation-fetch is not intended for use with Node.js, does removing it get rid of the memory leak? 🤔

[MSNev]

It would be extremely useful if you could identify the objects that are being retained and causing the out of memory. Along with maybe a small repo so that anyone can reproduce this without constructing their own version of the test.

[cpatti97100]

@cpatti97100 @opentelemetry/instrumentation-fetch is not intended for use with Node.js, does removing it get rid of the memory leak? 🤔

it does, but here #4063 I read "The motivation for this change is so I can instrument my NodeJS applications using fetch() with the @opentelemetry/instrumentation-fetch package.". Also here #3413 (comment) Node compatibility is mentioned. I guess I misunderstood something here or something is confusing :)

[pichlermarc]

@cpatti97100 @opentelemetry/instrumentation-fetch is not intended for use with Node.js, does removing it get rid of the memory leak? 🤔

it does, but here #4063 I read "The motivation for this change is so I can instrument my NodeJS applications using fetch() with the @opentelemetry/instrumentation-fetch package.". Also here #3413 (comment) Node compatibility is mentioned. I guess I misunderstood something here or something is confusing :)

Yes, sorry for the confusion - any support added was purely experimental. There are differences in Node's fetch and the web version. We plan on adding an undici instrumentation that will add support for Node.js' fetch (which uses Undici in the background). That'll then also be properly tested with Node.js (which is not the case with the fetch instrumentation currently).

In the meantime we'll change this instrumentation to be a no-op for Node.js to avoid any issues further issues like this.

That being said, it'd still be helpful to have a reproducer as MSNev said. It could be that this is not only affecting Node.js but also the browser instrumentation.

[cpatti97100]

sorry I am super busy right now :( but what I will do is to try out the implementation for undici which is under development and report if the same behavior still happens

[pichlermarc]

@cpatti97100 we've published the undici instrumentation recently. Would you be able to test that one out? 🙂

[lforst]

@cpatti97100 did you try the new undici instrumentation out yet? We're looking into using it for the Sentry Node.js SDK, and implicitly the Sentry Next.js SDK.

[david-luna]

@cpatti97100 any updates?