Very high CPU usage (at some point) with Postgres' capture

Hi there,

We have been using X-Ray for a few weeks now and we have had a few issues with some of our Node processes using 100% of CPU usage for no apparent reason.

**Details of the issue**

CPU and memory usage increases abruptly.

- Even after stopping any request to go to this container, the CPU stays at 100%, up until a certain point. Once it took 23 minutes, in the example above it's been more than an hour and is still at 100% CPU.

There are *many* `Segment too large to send` warning logs at the moment where the load starts to spike.

In the logs, the `trace_id` of the log itself (that we get with X-Ray's `getCurrentSegment()`) is different from the one in the log.

Profiling the Node process, we can see that X-Ray functions are the ones taking all the CPU. On a ~11seconds profile, this is the result.

**Questions**

- Do you have any idea of what might be the root cause?
- Do you have any idea of where to investigate next?