Memory leak in next/head

[asim-basraa]

Hello awesome nextjs team,

It took us few weeks to conclude that instability of our production app is due to next/head memory leak.
we have memory & cpu profiling log(can be loaded into chrome debugger) if someone want to check.

This issue is already reported few times ref: 1) fatal CPU usage growth with webpack externals & next/head , 2) next/head has a memory leak issue , 3)next/side-effect is not thread-safe and few more may be marked duplicated.
All these issues were goingto be fixed by [RFC] Deprecate next/head but this has been put on halt(close) with following comment

"Closing as AFAIK we're not sure next/head deprecation is required (per last meeting). @devknoll: let me know if we should reopen this." #9084 (comment) .

Our website has on average 8k-9k daily page visits and not to mention tens of thousands of google crawler calls. And with this memory leak it is becoming a showstopper for us as it requires a reboot after few hours.
As the root cause of this problem has already been found could someone please suggest a way forward for people in situation like us, may be an example of correctly using react-helment-async with latest Nextjs would unblock us. The official example in react-helment-async docs is still using next/head so really we need an example which does not use next/head.

best regards