Memory Leak in dd-trace http plugin about dd-trace-js

[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 even after requests are finished. If I replace it with cross-fetch, this span disappears.
   

[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?

[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