Custom Component Memory Leak

💬 App Building
, ,
1

We are seeing memory leaks when building custom components. After much pain and debugging we realised this is actually caused by using console from within the component. It seems something in the fullstory library overrides the native code with a custom implementation which leaks memory that is never recovered. Eventually it leads the retool-edge domain to crash.

If fullstory must exist at least provide access to the native function somehow as this creates a LOT of headaches when developing components.

  1. My goal: use console.log in custom components
  2. Issue: Fullstory overrides the native code with a leaky implementation
  3. Steps I've taken to troubleshoot: removing all the console logs. using chrome dev and performance tools
  4. Additional info: Cloud
3

Hi @james_at_alab,

Apologies for the issue and thank you for bringing this up and reporting this!

I can create a bug report for the Visibility team which owns our fullstory usage and let them know your suggestions on giving users access to the native functions.