Much time and memory consumed on structured clone

Add-ons Development
#1

I have researched on Firefox performance when our extension is enabled.
By using the profiler and about:memory, I found out that much memory and CPU time are consumed on structured cloning.

Screenshot 2023-07-02 at 19.14.01
Screenshot 2023-07-02 at 19.14.01693×346 72.8 KB

What is happening in this case and how to fix this problem?

1 Like
#2

I made an assumption that registering many onChanged handlers on storage is bad, and integrated many handlers into a single handler. Is this a right thing to do?