Memory Leak in dd-trace http plugin

[viral-barot]

I have encountered memory leak issue in dd-trace package.
when I disable http plugin DD_TRACE_DISABLED_INSTRUMENTATIONS=http then there is no memory leak.

I have tried with upgrading and downgrading dd-trace package versions between 3.X to 5.X also tried different node version but still facing same issue.

node version : 18.17.1
dd-trace version : 5.10.0
restify version : 11.1.0

Memory Heap Snapshot

http plugin Disabled - Heap Snapshot.zip

http plugin Enabled - Heap Snapshot.zip

[sunsheeppoplar]

@tlhunter sorry for the tag, not sure the protocol for raising issues up to folks at dd... wondering if this is being looked at in the v4 and v5 lines

[SkylerRogers]

I am too having this issue. We're seeing elevated memory footprint in our node application after upgrading dd-trace npm package. Has anyone on the DataDog side been able to confirm this?

[ZeroCho]

for me, using cross-fetch instead of Native Node.js fetch solved memory leak. I guess something is wrong with dc-polyfill. Every fat span of continuous profiler is related with fetch code.

1. waitForImage method calls 'fetch' which remains in memory even after waitForImage method ends and this span disappears if I replace it with cross-fetch
   
2. replicate use fetch internally and it remains in memory after finished. If I replace it with cross-fetch, this span disappears.