We did a release two days ago that bumped many packages including a cls-rtracer bump from 2.6.0 to 2.6.1.
We quickly started experiencing memory leaks on all our services as shown below (sample).
We did rollback the release and then released again yesterday. By dumping the memory I did come to the conclusion that cls-rtracer@2.6.1 was leaking. After rollbacking to 2.6.0 and deploying everything again, leaks have disappeared.
Can't share full heapdump but I did saw a pattern of increasing memory usage of cls-rtracer objects.
Hello,
We did a release two days ago that bumped many packages including a cls-rtracer bump from
2.6.0
to2.6.1
. We quickly started experiencing memory leaks on all our services as shown below (sample).We did rollback the release and then released again yesterday. By dumping the memory I did come to the conclusion that cls-rtracer@2.6.1 was leaking. After rollbacking to 2.6.0 and deploying everything again, leaks have disappeared.
Can't share full heapdump but I did saw a pattern of increasing memory usage of cls-rtracer objects.
Then 7 minutes later
Also
Then 7 minutes later